On Mon, Nov 16, 2015 at 4:19 PM, Toon Moene <t...@moene.org> wrote: > On 11/16/2015 10:11 PM, Jack Howarth wrote: > >> On Mon, Nov 16, 2015 at 2:14 PM, Toon Moene <t...@moene.org> wrote: > > >>> To put this in a (timeline) perspective: >>> >>> On the 18th of March, 2000, I announced Andy Vaught's work on the g95 >>> front-end to the gcc-patches mailing list. >>> >>> In 2004 (!) we merged the resulting compiler and run-time library into >>> the >>> gcc (cvs) repository (obviously, after the tree-ssa infrastructure went >>> in - >>> 2004-05-17, but before the creation of the 4.0 release branch - >>> 2005-02-25). >>> Then it took another 2 months for 4.0 to be released. >>> >>> Unless PGI manages to summon massively large (parallel) working groups to >>> accomplish this, it might take a few years to fruition. >>> >> >> On the other hand, the llvm-dev posting implies that PGI will be >> starting from an existing fortran front-end. If they only need to code >> the middle-/back-end integration of llvm into a pre-existing mature >> fortran front-end, the promised late 2016 release date might not be so >> unlikely. > > > The g95 front-end I mentioned in my 2000-03-18 post to the gcc-patches > mailing list was "an existing front-end" by virtue of the fact that Andy > Vaught mailed it to me and it did the work. > > Between 2000 and 2004, this front-end was coupled to the rest of the > infrastructure of the GNU Compiler Collection. This was not trivial (just as > it will not be trivial to couple the PGI front-end to the LLVM > infrastructure). > > We'll see how many years it'll take, but don't count me in on holding my > breath. >
Of course one unknown is whether PGI had already done any work internally with the llvm middle-/back-end. If so, they might not be starting from scratch. > > -- > Toon Moene - e-mail: t...@moene.org - phone: +31 346 214290 > Saturnushof 14, 3738 XG Maartensdijk, The Netherlands > At home: http://moene.org/~toon/; weather: http://moene.org/~hirlam/ > Progress of GNU Fortran: http://gcc.gnu.org/wiki/GFortran#news
