[llvm-dev] Adapting and open-sourcing PGI's Fortran frontend for LLVM

[Chad Rosier via llvm-dev]

All excellent news!  Thanks for the update, Doug!

-----Original Message-----
From: douglas miles (PGI) [mailto:douglas.miles at pgroup.com] 
Sent: Thursday, May 26, 2016 2:58 PM
To: Hal Finkel <hfinkel at anl.gov>; mcrosier at codeaurora.org
Cc: flang-dev <flang-dev at googlegroups.com>; Rob Neely <neely4 at llnl.gov>; Chris Lattner <clattner at apple.com>; llvm-dev at lists.llvm.org
Subject: RE: [llvm-dev] Adapting and open-sourcing PGI's Fortran frontend for LLVM

Hi Chad - We have a functional Fortran compiler, with the PGI front-end bridged directly to LLVM, all of our Fortran runtime libraries integrated, and the Clang driver adapted for use with the Fortran compiler.  We're working with a few users at DOE who are trying to compile big applications with a binary version of the compiler.  Work is ongoing to migrate the source code into an LLVM-style repository, build infrastructure, documentation and web pages.  All of the compiler and runtime source is now built with Clang or the Fortran front-end with LLVM.  Much work remains on source code refactoring and documentation;  we expect that work to accelerate once all the infrastructure work is done.

Doug

-----Original Message-----
From: Hal Finkel [mailto:hfinkel at anl.gov] 
Sent: Thursday, May 26, 2016 9:17 AM
To: mcrosier at codeaurora.org
Cc: flang-dev; douglas miles (PGI); Rob Neely; Chris Lattner; llvm-dev at lists.llvm.org
Subject: Re: [llvm-dev] Adapting and open-sourcing PGI's Fortran frontend for LLVM

Hi Chad,

I can tell you that progress is being made on PGI's side; I'll let Doug/Rob provide more detailed updates.

 -Hal

----- Original Message -----
> From: "Chad Rosier" <mcrosier at codeaurora.org>
> To: "Hal Finkel" <hfinkel at anl.gov>
> Cc: "flang-dev" <flang-dev at googlegroups.com>, "douglas miles (PGI)" <douglas.miles at pgroup.com>, "Rob Neely"
> <neely4 at llnl.gov>, "Chris Lattner" <clattner at apple.com>, 
> llvm-dev at lists.llvm.org
> Sent: Thursday, May 26, 2016 10:47:19 AM
> Subject: RE: [llvm-dev] Adapting and open-sourcing PGI's Fortran frontend	for	LLVM
> 
> Hi Hal,
> I haven't been following this closely, but has there been any updates 
> recently.
> 
>  Regards,
>   Chad
> 
> -----Original Message-----
> From: llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org] On Behalf Of 
> Chris Lattner via llvm-dev
> Sent: Sunday, November 15, 2015 12:46 AM
> To: Hal Finkel <hfinkel at anl.gov>
> Cc: LLVM Dev <llvm-dev at lists.llvm.org>; flang-dev 
> <flang-dev at googlegroups.com>; douglas miles (PGI) 
> <douglas.miles at pgroup.com>; Rob Neely <neely4 at llnl.gov>
> Subject: Re: [llvm-dev] Adapting and open-sourcing PGI's Fortran 
> frontend for LLVM
> 
> 
> > On Nov 13, 2015, at 2:22 PM, Hal Finkel via llvm-dev 
> > <llvm-dev at lists.llvm.org> wrote:
> > 
> > Hi everyone,
> > 
> > I have some very good news for everyone interested a 
> > production-quality Fortran frontend for LLVM:
> > 
> > The U.S. Department of Energy’s National Nuclear Security 
> > Administration and its three national labs have reached an agreement 
> > with NVIDIA's PGI division to adapt and open-source PGI's Fortran 
> > frontend, and associated Fortran runtime library, for contribution 
> > to the LLVM project. PGI is now working on isolating the necessary 
> > frontend components from their existing compiler code base and 
> > adapting those components to produce LLVM IR for consumption by our 
> > existing infrastructure.
> 
> This sounds very interesting Hal (and Doug), and I’m glad to hear 
> about it.  I look forward to when more details and code is available,
> 
> -Chris
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
> 
> 

--
Hal Finkel
Assistant Computational Scientist
Leadership Computing Facility
Argonne National Laboratory

-----------------------------------------------------------------------------------
This email message is for the sole use of the intended recipient(s) and may contain
confidential information.  Any unauthorized review, use, disclosure or distribution
is prohibited.  If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.
-----------------------------------------------------------------------------------