In spring 2020 the llvm f18 fortran compiler code landed in the llvm11 trunk renamed as flang.
I'm just a ports user that depends on a few ports that use gfortran, so I won't demand action, but devel/flang devel/flang-clang still depend on devel/llvm70 and devel/f18 depends on devel/llvm80.
Is there a way to update these and/or provide an option in llvm11/llvm-devel to build the new flang to reflect the progress the llvm project has made?
I'm interested in enabling flang in llvm11 and llvm-devel, but have been quite busy at work and not found time to investigate what's involved (I imagine llvm-devel just requires adding an option and turning it on if it works on FreeBSD at all.)
A commit references this bug:
Date: Fri Aug 14 18:35:41 UTC 2020
New revision: 544895
Update to a new snapshot and add FLANG and MLIR options
Add two new options:
- FLANG (Fortran 2018 compiler)
- MLIR (Multi-Level Intermediate Representation support)
MLIR is enabled by default and required by FLANG. FLANG is not yet
enabled by default because it is broken with LLVM_LINK_LLVM_DYLIB=ON
which results in a truly enormous package (500+MB .txz).
Sponsored by: DARPA
What is the status of this PR?
Most likely these ports should just be deleted at some point. They are unlikely to be updated. I've not circled back to flang to see if it now builds with LLVM_LINK_LLVM_DYLIB=ON so haven't tried enabling it by default in llvm-devel.
(In reply to Brooks Davis from comment #4)
OK. There is one reverse dependency according to INDEX though, math/py-pynleq2, which is also a leaf port.
(In reply to Rene Ladan from comment #5)
math/py-pynleq2 does not depend on flang anymore as of r565258
I'll give it a spin. I have an old Fortran IV program from the mainframe that prints Snoopy calendars. If it builds something runable that doesn't hang it'll work with almost anything.
FYI, devel/llvm70 does not depend on Python 2.7 anymore.