MAINT,DOC: Classic Flang is not LLVM Flang #20240

Activity

1. HaoZeke

   added

   good first issue

   component: numpy.distutils

   03 - Maintenance

   on Oct 30, 2021
2. HaoZeke commented on Oct 30, 2021

   

   HaoZeke

   on Oct 30, 2021

   Last edited by HaoZeke

   MemberAuthor

   More actions

   Also while we're at it we might as well kill off (in separate commits) the other unmaintained Fortran compilers. However I'm less concerned about them, since there is no confusion about the other compilers.
3. rgommers

   removed

   good first issue

   on Oct 30, 2021
4. rgommers commented on Oct 30, 2021

   

   rgommers

   on Oct 30, 2021

   Member

   More actions

   I don't think this is a good first issue. We cannot just remove this. Right now Classic Flang still has more functionality I believe, in particular on Windows.

   We may add LLVM-FLang as a new compiler and improve the docs.
5. rgommers commented on Oct 30, 2021

   

   rgommers

   on Oct 30, 2021

   Member

   More actions

   Also, Classic Flang is not unmaintained. As of right now it's my best hope at a sane Fortran story for SciPy within the next year.
6. HaoZeke commented on Oct 30, 2021

   

   HaoZeke

   on Oct 30, 2021

   MemberAuthor

   More actions

   Ah, I think I made a bit of a knee jerk assumption based off their wiki which states that it should be considered to be superseded by F18 from early 2020.

   However, the impetus was that at-least in the context of clang and flang optimizations as discussed in #19930, classic flang is incorrect.

   Naming the fortran compilers is a bit of a nightmare, perhaps classic_flang and flang for LLVM would make more sense for the issue?
7. rgommers commented on Oct 30, 2021

   

   rgommers

   on Oct 30, 2021

   Member

   More actions

   Naming the fortran compilers is a bit of a nightmare, perhaps classic_flang and flang for LLVM would make more sense for the issue?

   I think I'd prefer a non-breaking change. Can we just add some code comments for now that flang means classic, and name the new one flang_llvm? Or maybe rename the other classic_flang but keep flang as an alias to that one (I think that is possible)? Once the new one actually is the better compiler, we can then switch flang. My impression is that that's a couple of years away still.

   👀React with 👀1Reacted by Rohit Goswami
8. HaoZeke commented on Oct 30, 2021

   

   HaoZeke

   on Oct 30, 2021

   Last edited by HaoZeke

   MemberAuthor

   More actions

   Or maybe rename the other classic_flang but keep flang as an alias to that one (I think that is possible)?

   This sounds like a plan. Will do. Thanks!

   My impression is that that's a couple of years away still.

   Yup, sounds about right. MLIR itself is still in a lot of flux too.
9. charris

   closed this as completedin #24532on Sep 5, 2023