<div dir="ltr">Hi Petr-<div><br></div><div>Both the benchmarks run. We are currently working on fotonik and roms. </div><div><br></div><div>We will support some of Fortran 2003 features soon.</div><div><br></div><div>thanks,</div><div>-Prashanth </div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Feb 20, 2020 at 11:57 AM Petr Penzin <<a href="mailto:penzin.dev@gmail.com">penzin.dev@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
<div>
<p>Hi Prashanth,</p>
<p>Do those benchmarks run? They seem to be relatively short (bwaves
[1], exchange [2]), but if the runs verify correctly that would be
pretty good.<br>
</p>
<p> Do you plan on supporting any of the Fortran 2003 features?</p>
<p><br>
</p>
<p>-Petr<br>
</p>
<p>[1]:
<a href="https://www.spec.org/cpu2017/Docs/runcpu-avoidance.html#pickone" target="_blank">https://www.spec.org/cpu2017/Docs/runcpu-avoidance.html#pickone</a><br>
</p>
<p>[2]:
<a href="https://www2.hawaii.edu/~nreed/ics606/papers/Metcalf06Sudoku.pdf" target="_blank">https://www2.hawaii.edu/~nreed/ics606/papers/Metcalf06Sudoku.pdf</a><br>
</p>
<div>On 2/17/20 9:19 AM, Prashanth N R
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div>Hi Petr-</div>
<div><br>
</div>
<div>1. We compile SPEC benchmarks bwaves and xchange currently.
We are close to compiling fotonik at this point. </div>
<div>2. We released the source as experimental for the community
to take a look. Soon we will open source the entire history of
development(we are working on the script to upload the
history).</div>
<div><br>
</div>
<div>thanks,</div>
<div>-Prashanth</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Mon, Feb 10, 2020 at 4:20
AM Petr Penzin via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
<div><br>
*FC*<br>
<a href="https://github.com/compiler-tree-technologies/fc" target="_blank">https://github.com/compiler-tree-technologies/fc</a><br>
Not related to any of the above, but seems to be in some
ways similar to Clang/(old)Flang/Fort. Recursive descent
parser; emits MLIR. Does not use tablegen, has a different
way of throwing errors, has no builtin diagnostics, also
no driver. Project has only seven commits to this date.
Not clear on the Fortran standard support (has flags to
support f77 and f95), the claim that it can compile a
couple of larger application from SPEC, but I can't find
which ones.<br>
<br>
<br>
<div>On 1/13/20 9:02 AM, James Y Knight via llvm-dev
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">Neat, another fortran compiler
option.
<div><br>
</div>
<div>Does anyone have a list/comparison of all the
LLVM fortran compilers? I'm not really tracking
this, since Fortran isn't really my area of
expertise, but I've seen the following. Perhaps
there are even more?
<div>
<div><br>
</div>
<div>"Flang". The original of the name, I
think? Abandoned.<br>
<a href="https://github.com/llvm-flang/flang" target="_blank">https://github.com/llvm-flang/flang</a><br>
"Fort" -- fork of the above flang, renamed.
Seems active.<br>
<a href="https://github.com/llvm-fortran/fort/" target="_blank">https://github.com/llvm-fortran/fort/</a><br>
<br>
</div>
<div>"Flag". Different from the other "flang".
Active, but deprecated in favor of f18.</div>
<div><a href="https://github.com/flang-compiler/flang" target="_blank">https://github.com/flang-compiler/flang</a><br>
</div>
<div>"f18". Rewrite-from-scratch (?) of
adjacent "flang". Active, but not
fully-functional yet (I think?).</div>
<div><a href="https://github.com/flang-compiler/f18" target="_blank">https://github.com/flang-compiler/f18</a><br>
</div>
<div><br>
</div>
<div>
<div>"FC". Newly-developed, independent of
the other compilers. Active. (But this
source-code dates from the previous
announcement, not yet updated with latest
developments):<br>
<a href="https://github.com/compiler-tree-technologies/fc" target="_blank">https://github.com/compiler-tree-technologies/fc</a><br>
</div>
</div>
<div><br>
</div>
<div>I don't know how any of these compare
with each other, nor why we have so many. I
have no opinion on which or whether any of
these should be "blessed", nor do I really
want to become educated enough on this topic
to gain such an opinion personally.</div>
<div><br>
</div>
<div>But, given that there appear to be at
least 3 fortran compilers under active
development by different people, I would
love to be reassured that such a comparison
has been done, and that we are selecting one
of them for good reasons. It'd be great if
someone (or multiple someones) could post a
summary/comparison of what these things all
are, and why one is the right path forward
vs another.</div>
</div>
</div>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Mon, Jan 13,
2020 at 2:46 AM Prashanth N R via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
<div dir="ltr">Hi Chris-
<div>We are mostly cleaning up the code for open
sourcing. Early code drop will happen in a day
or two and will continue through this week. We
would love to work with the rest of the
community on this. </div>
<div><br>
</div>
<div>thanks,</div>
<div>-Prashanth</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Mon, Jan
13, 2020 at 11:17 AM Chris Lattner <<a href="mailto:clattner@nondot.org" target="_blank">clattner@nondot.org</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
<div>Agreed! Is the code already available?
What are your plans for it, and are you
interested in collaboration with the rest of
the LLVM community?
<div><br>
</div>
<div>-Chris<br>
<div><br>
<blockquote type="cite">
<div>On Jan 11, 2020, at 11:58 AM,
Finkel, Hal J. via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a>>
wrote:</div>
<br>
<div>
<div>
<p>Hi, Prashanth,</p>
<p>That's great news! It sounds
like you've made a lot of
progress, and I certainly hope
that you can make your source
available under the LLVM license
and that we can all work
together going forward.</p>
<p> -Hal<br>
</p>
<div>On 1/11/20 12:52 PM,
Prashanth N R via llvm-dev
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">Hi-
<div><br>
</div>
<div>In August we made an
announcement of "FC: A new
fortran front end" [1]. At
that time to get an
end-to-end solution, we made
FC to emit LLVM IR
directly. At present, we
have upgraded FC to emit
MLIR. Currently the language
supported is close to
Fortran-95. Apart from 400+
unit test cases, out
framework passes two
SPEC-2017 benchmarks
successfully. Currently we
are cleaning up the code and
plan to open source the same
in a week or so.</div>
<div><br>
</div>
<div>Apart from the front end
changes, we have defined a
new high level dialect in
MLIR for representing
Fortran. We have defined a
new Loop Nest Optimization
framework along with one
Loop Nest Optimization in it
for the time being. Also we
have supported 4 OpenMP
constructs and way to
express the same in MLIR
framework. </div>
<div><br>
</div>
<div>Entire code is in the
spirit of LLVM. If the
community is interested, we
would like to work with the
community and move forward. </div>
<div><br>
</div>
<div>thanks,</div>
<div>-Prashanth</div>
<div><br>
</div>
<div>PS: We did try to use F18
for a while and hit the
issues raised in [2], [3].</div>
<div><br>
</div>
<div>1. <a href="http://lists.llvm.org/pipermail/llvm-dev/2019-August/134620.html" target="_blank">http://lists.llvm.org/pipermail/llvm-dev/2019-August/134620.html</a></div>
<div>2. <a href="http://lists.llvm.org/pipermail/llvm-dev/2020-January/138069.html" target="_blank">http://lists.llvm.org/pipermail/llvm-dev/2020-January/138069.html</a></div>
<div>3. <a href="http://lists.llvm.org/pipermail/flang-dev/attachments/20191202/6e7c1e51/attachment-0001.pdf" target="_blank">http://lists.llvm.org/pipermail/flang-dev/attachments/20191202/6e7c1e51/attachment-0001.pdf</a></div>
<div>OR <a href="http://lists.llvm.org/pipermail/flang-dev/2019-December/000089.html" target="_blank">http://lists.llvm.org/pipermail/flang-dev/2019-December/000089.html</a></div>
<div><br>
</div>
</div>
<br>
<fieldset></fieldset>
<pre>_______________________________________________
LLVM Developers mailing list
<a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a>
<a href="https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev" target="_blank">https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a>
</pre>
</blockquote>
<pre cols="72">--
Hal Finkel
Lead, Compiler Technology and Programming Languages
Leadership Computing Facility
Argonne National Laboratory</pre>
</div>
_______________________________________________<br>
LLVM Developers mailing list<br>
<a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a><br>
<a href="https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev" target="_blank">https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a><br>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</blockquote>
</div>
_______________________________________________<br>
LLVM Developers mailing list<br>
<a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a><br>
<a href="https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev" rel="noreferrer" target="_blank">https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a><br>
</blockquote>
</div>
</div>
<br>
<fieldset></fieldset>
<pre>_______________________________________________
LLVM Developers mailing list
<a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a>
<a href="https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev" target="_blank">https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a>
</pre>
</blockquote>
</div>
_______________________________________________<br>
LLVM Developers mailing list<br>
<a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a><br>
<a href="https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev" rel="noreferrer" target="_blank">https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a><br>
</blockquote>
</div>
</div>
</blockquote>
</div>
</blockquote></div>