-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When will flang-new be brought in ? General roadmap question about aomp wrt Fortran. #971
Comments
Hi Joe, we are working very hard on flang-new. It is hard to make statements about the future here. It is obvious from upstream LLVM activity that a lot of work for flang-new is upstream. But it is not ready to switch from flang-legacy to flang-new. |
Now that flang-new appears to be in ROCm 6.3, can we now discuss what specific features are now imparted on the amdflang compiler included with ROCm? From reading other issues related to this one, it appears that amdflang is no longer pointing to flang-legacy. All ROCm docs suggest that AMD just got equipped with a Fortran compiler, which is not really quite true (amdflang has been around for some time ...). What features specifically come with the new compiler? |
Hi Joe, we have not added flang-new to ROCm 6.3 , not sure where you are seeing this. could you point me at a couple of the links that you mentioned ? |
I supppose I'm confused in general about the announcement of the "next-gen fortran compiler" (https://rocm.blogs.amd.com/ecosystems-and-partners/fortran-journey/README.html) ... |
The blog post refers to a preview of the new fortran compiler, an important snippet: AMD’s Next-Gen Fortran Compiler will be a downstream flavor of LLVM Flang and will in time supplant the current AMD Flang compiler, a downstream flavor of “Classic Flang”. |
Got it. It appears the messaging is getting muddied elsewhere, including in comments from cloud providers offering MI300X |
The support for fortran codes in general within ROCm is quite embarrassing.
A number of projects I've worked on for folks at Pawsey, in addition to some of our own projects ( e.g. https://github.com/fluidnumerics/SELF) , that use derived types with type bound procedures, inheritance, and polymorphic types simply don't compile with aomp (separate issues will be open soon) when gpu offloading via openmp is enabled.
It'd be helpful to have some clarification on some rather vague comments (from this issue : #576 (comment) ). Specifically
What is meant by "limited offloading support" ?
When will ROCm actually have a production fortran compiler via llvm flang-new ?
To extend on this, what Fortran language standard will be fully supported ?
The text was updated successfully, but these errors were encountered: