[Flang-dev] [llvm-dev] flang in llvm.org source tree

xoviat xoviat at gmail.com
Mon Oct 15 16:31:46 EDT 2018


Does anyone know for sure whether f18 will require the clang front end? My largest complaint about the current flang design is that it requires a patch to the clang to be able to work, which significantly increases repackaging costs. In my personal flang tree, I wrote a new front end so that my version of flang could be built with the stock clang and LLVM, which allows me to upgrade clang and recompile whenever a new LLVM version comes out. I would greatly encourage the NVIDIA developers to do the same for f18.

I also noticed that when attempting to compile f18, even the latest version of clang-cl had trouble handling some of the methods that contained heavy used of std::visit, while Microsoft’s compiler experienced certain internal compiler errors. I hope that these issues will be resolved by the time that flang development is stopped.

From: David Greene
Sent: Monday, October 15, 2018 3:22 PM
To: Jack Howarth
Cc: llvm-dev; flang-dev at lists.flang-compiler.org
Subject: Re: [Flang-dev] [llvm-dev] flang in llvm.org source tree

Yes, the projects are proceeding in parallel.  As far as I understand
things, development of "flang" will stop when "f18" reaches feature
parity.  You would have to ask the NVIDIA people for more information.
I'm just going on information presented at the Webinar a couple of
months back.

                           -David

Jack Howarth via llvm-dev <llvm-dev at lists.llvm.org> writes:

> Now I'm really confused as the 'flang' compiler here has lots of
> recent commits from the Portland Group...
>
> https://github.com/flang-compiler/flang/commits/master
>
> On Mon, Oct 15, 2018 at 10:54 AM David Greene <dag at cray.com> wrote:
>
>     Seems like this should also go to flang-dev so I'm adding it.
>     
>     "flang" is basically a legacy project. "f18" is the new ground-up
>     build
>     of a Fortran LLVM project. f18 is the thing that has the most
>     likelihood of becoming an "official" LLVM project.
>     
>     However, it's probably going to be a while before we get there.
>     For one
>     thing, I haven't seen any posts on flang-dev that talk about
>     making
>     changes to f18, proposing designs, etc. The development seems
>     completely opaque right now, which is unfortunate.
>     
>     I would like to see f18 become "official" sooner rather than
>     later, both
>     to open up development and to get better code sharing across
>     projects.
>     
>     -David
>     
>     Jack Howarth via llvm-dev <llvm-dev at lists.llvm.org> writes:
>     
>     > Is there a schedule for when flang will be merged into the
>     official
>     > llvm.org svn/git source trees instead of having to do standalone
>     > custom builds with additional patches?
>     > Jack
>     >
>     > _______________________________________________
>     > LLVM Developers mailing list
>     > llvm-dev at lists.llvm.org
>     > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev

_______________________________________________
flang-dev mailing list
flang-dev at lists.flang-compiler.org
http://lists.flang-compiler.org/mailman/listinfo/flang-dev_lists.flang-compiler.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.flang-compiler.org/pipermail/flang-dev_lists.flang-compiler.org/attachments/20181015/2c73e75e/attachment.html>


More information about the flang-dev mailing list