[flang-dev] [llvm-dev] [11.0.0 Release] The release branch is here; trunk is now 12.0.0
Richard Barton via flang-dev
flang-dev at lists.llvm.org
Thu Jul 16 02:38:29 PDT 2020
Hi Hans, Rainer
I can describe the status of Flang, but I am not exactly sure what the criteria is for a sub-project to be ready for release testing. If there is anything missing from my summary please ask.
Functionally, Flang is able to parse Fortran but is not able to generate the corresponding LLVM IR. Flang supports a mode where it unparses the parsed Fortran back to Fortran source and then passes it off to another Fortran compiler that the user can chose to do codegen.
In terms of platform support, flang does not support the full list of LLVM compilers due to its C++17 requirements, so allowances would need to be made for that. We know for sure that Flang does not yet build on Windows yet, so we would need to also make an exception for this in LLVM 11 release. With downstream testing across the community, we believe that Flang should work well for the subset of supported compilers on unix distros on Arm and x86_64. Flang is still not well covered by public buildbots. We have some for Arm on Ubuntu with modern GCC and clang releases but we lack coverage for other distros and other CPU architectures, notably X86_64. We have only just fixed shared library builds (on linux) and we'll be asking to cherry pick those fixes to the LLVM 11 release branch.
Because of the above, flang does not build as a default target and does not build even with -DLLVM_ENABLE_PROJECTS=all.
I believe/assume that there is no Fortran code in LNT. If there is, we certainly have not tested Flang against it so might expect issues. If I am right and there is no Fortran code in the test suite then clearly it is not useful to run it for Flang.
Our thoughts as a community were that we would document the flang status in the LLVM 11 release notes so that folks taking the release as source could experiment with it if they wanted to. I don't think anyone had a strong feeling for whether we should include the pre-built binaries in a release.
I would certainly not be against trying to add flang here and seeing how well it does against the release build and test process and give us feedback for things to work on. On the other hand, I would not want to cause undue disruption to the release effort, so I think there needs to be appetite to try amongst the release testers as well.
@Hans Based on this, do you think it would be a good idea to add flang to the script at this stage?
> -----Original Message-----
> From: llvm-dev <llvm-dev-bounces at lists.llvm.org> On Behalf Of Hans
> Wennborg via llvm-dev
> Sent: 15 July, 2020 13:42
> To: Rainer Orth <ro at gcc.gnu.org>
> Cc: Hans Wennborg via llvm-dev <llvm-dev at lists.llvm.org>; Release-testers
> <release-testers at lists.llvm.org>; flang-dev at lists.llvm.org
> Subject: Re: [llvm-dev] [11.0.0 Release] The release branch is here; trunk is
> now 12.0.0
> On Wed, Jul 15, 2020 at 2:20 PM Rainer Orth <ro at gcc.gnu.org> wrote:
> > Hi Hans,
> > > The release branch for LLVM 11 was created from the trunk at
> > > 2e10b7a39b930ef8d9c4362509d8835b221fbc0a, and the trunk version was
> > > bumped to 12.0.0.
> > [...]
> > > The first release candidate will be tagged soon (hopefully in a day or
> > > two if the branch looks stable), and testing of that can begin. The
> > > full release schedule can be found under "Upcoming Releases" to the
> > > right at https://llvm.org
> > I noticed that the test-release.sh script currently lacks support to
> > include flang in the build. Is this intentional or just an oversight?
> It hasn't been added yet since flang wasn't in the tree for the last release.
> flang-dev folks: what is the current flang status? Should it be added
> to the llvm/utils/release/test-release.sh script so that it gets
> testing and prebuilt binaries as part of the release?
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
More information about the flang-dev