<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang=EN-US link=blue vlink="#954F72"><div class=WordSection1><p class=MsoNormal>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.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>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.</p><p class=MsoNormal><o:p> </o:p></p><div style='mso-element:para-border-div;border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal style='border:none;padding:0in'><b>From: </b><a href="mailto:dag@cray.com">David Greene</a><br><b>Sent: </b>Monday, October 15, 2018 3:22 PM<br><b>To: </b><a href="mailto:howarth.mailing.lists@gmail.com">Jack Howarth</a><br><b>Cc: </b><a href="mailto:llvm-dev@lists.llvm.org">llvm-dev</a>; <a href="mailto:flang-dev@lists.flang-compiler.org">flang-dev@lists.flang-compiler.org</a><br><b>Subject: </b>Re: [Flang-dev] [llvm-dev] flang in llvm.org source tree</p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Yes, the projects are proceeding in parallel. As far as I understand</p><p class=MsoNormal>things, development of "flang" will stop when "f18" reaches feature</p><p class=MsoNormal>parity. You would have to ask the NVIDIA people for more information.</p><p class=MsoNormal>I'm just going on information presented at the Webinar a couple of</p><p class=MsoNormal>months back.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal> -David</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Jack Howarth via llvm-dev <llvm-dev@lists.llvm.org> writes:</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>> Now I'm really confused as the 'flang' compiler here has lots of</p><p class=MsoNormal>> recent commits from the Portland Group...</p><p class=MsoNormal>><o:p> </o:p></p><p class=MsoNormal>> https://github.com/flang-compiler/flang/commits/master</p><p class=MsoNormal>><o:p> </o:p></p><p class=MsoNormal>> On Mon, Oct 15, 2018 at 10:54 AM David Greene <dag@cray.com> wrote:</p><p class=MsoNormal>><o:p> </o:p></p><p class=MsoNormal>> Seems like this should also go to flang-dev so I'm adding it.</p><p class=MsoNormal>> </p><p class=MsoNormal>> "flang" is basically a legacy project. "f18" is the new ground-up</p><p class=MsoNormal>> build</p><p class=MsoNormal>> of a Fortran LLVM project. f18 is the thing that has the most</p><p class=MsoNormal>> likelihood of becoming an "official" LLVM project.</p><p class=MsoNormal>> </p><p class=MsoNormal>> However, it's probably going to be a while before we get there.</p><p class=MsoNormal>> For one</p><p class=MsoNormal>> thing, I haven't seen any posts on flang-dev that talk about</p><p class=MsoNormal>> making</p><p class=MsoNormal>> changes to f18, proposing designs, etc. The development seems</p><p class=MsoNormal>> completely opaque right now, which is unfortunate.</p><p class=MsoNormal>> </p><p class=MsoNormal>> I would like to see f18 become "official" sooner rather than</p><p class=MsoNormal>> later, both</p><p class=MsoNormal>> to open up development and to get better code sharing across</p><p class=MsoNormal>> projects.</p><p class=MsoNormal>> </p><p class=MsoNormal>> -David</p><p class=MsoNormal>> </p><p class=MsoNormal>> Jack Howarth via llvm-dev <llvm-dev@lists.llvm.org> writes:</p><p class=MsoNormal>> </p><p class=MsoNormal>> > Is there a schedule for when flang will be merged into the</p><p class=MsoNormal>> official</p><p class=MsoNormal>> > llvm.org svn/git source trees instead of having to do standalone</p><p class=MsoNormal>> > custom builds with additional patches?</p><p class=MsoNormal>> > Jack</p><p class=MsoNormal>> ></p><p class=MsoNormal>> > _______________________________________________</p><p class=MsoNormal>> > LLVM Developers mailing list</p><p class=MsoNormal>> > llvm-dev@lists.llvm.org</p><p class=MsoNormal>> > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</p><p class=MsoNormal>><o:p> </o:p></p><p class=MsoNormal>> _______________________________________________</p><p class=MsoNormal>> LLVM Developers mailing list</p><p class=MsoNormal>> llvm-dev@lists.llvm.org</p><p class=MsoNormal>> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>_______________________________________________</p><p class=MsoNormal>flang-dev mailing list</p><p class=MsoNormal>flang-dev@lists.flang-compiler.org</p><p class=MsoNormal>http://lists.flang-compiler.org/mailman/listinfo/flang-dev_lists.flang-compiler.org</p><p class=MsoNormal><o:p> </o:p></p></div></body></html>