<div dir="ltr">Hi Chris/Hal-<div><br></div><div>[2/3]</div><div>As agreed we are open sourcing implementation of 5 Openmp constructs i.e. omp.parallel, omp.single, omp.do, omp.master and omp.parallel_do. The latest code can be accessed at <a href="https://github.com/compiler-tree-technologies/">https://github.com/compiler-tree-technologies/</a>fc . Along with LLVM fork the repository can be accessed at <a href="https://github.com/compiler-tree-technologies/">https://github.com/compiler-tree-technologies/</a> . Testing infrastructure has been upgraded to Lit framework. Openmp test cases can be accessed at <a href="https://github.com/compiler-tree-technologies/fc/tree/master/test/openmp">https://github.com/compiler-tree-technologies/fc/tree/master/test/openmp</a> . Implementation of rest of the constructs will be open sourced in a later release. Please give feedback on the implementation and report any issues you encounter. </div><div><br></div><div>A detailed design note along with the issues considered will be sent shortly to the group for discussion. </div><div><br></div><div>Thanks,</div><div>-Prashanth</div><div><br></div><div>PS: In the next release we will opensource implementation of some loop transforms like Loop Blocking, Loop Permute(generalized interchange) etc.</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">clattner@nondot.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="overflow-wrap: break-word;">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>