Prashanth N R via llvm-dev
2020-Jan-11 18:52 UTC
[llvm-dev] FC : A MLIR+LLVM based Fortran front end
Hi- 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. 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. Entire code is in the spirit of LLVM. If the community is interested, we would like to work with the community and move forward. thanks, -Prashanth PS: We did try to use F18 for a while and hit the issues raised in [2], [3]. 1. http://lists.llvm.org/pipermail/llvm-dev/2019-August/134620.html 2. http://lists.llvm.org/pipermail/llvm-dev/2020-January/138069.html 3. http://lists.llvm.org/pipermail/flang-dev/attachments/20191202/6e7c1e51/attachment-0001.pdf OR http://lists.llvm.org/pipermail/flang-dev/2019-December/000089.html -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20200112/cd637ec4/attachment.html>
Finkel, Hal J. via llvm-dev
2020-Jan-11 19:58 UTC
[llvm-dev] FC : A MLIR+LLVM based Fortran front end
Hi, Prashanth, 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. -Hal On 1/11/20 12:52 PM, Prashanth N R via llvm-dev wrote: Hi- 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. 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. Entire code is in the spirit of LLVM. If the community is interested, we would like to work with the community and move forward. thanks, -Prashanth PS: We did try to use F18 for a while and hit the issues raised in [2], [3]. 1. http://lists.llvm.org/pipermail/llvm-dev/2019-August/134620.html 2. http://lists.llvm.org/pipermail/llvm-dev/2020-January/138069.html 3. http://lists.llvm.org/pipermail/flang-dev/attachments/20191202/6e7c1e51/attachment-0001.pdf OR http://lists.llvm.org/pipermail/flang-dev/2019-December/000089.html _______________________________________________ LLVM Developers mailing list llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev -- Hal Finkel Lead, Compiler Technology and Programming Languages Leadership Computing Facility Argonne National Laboratory -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20200111/8bfb06b4/attachment.html>
Chris Lattner via llvm-dev
2020-Jan-13 05:47 UTC
[llvm-dev] FC : A MLIR+LLVM based Fortran front end
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? -Chris> On Jan 11, 2020, at 11:58 AM, Finkel, Hal J. via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Hi, Prashanth, > > 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. > > -Hal > > On 1/11/20 12:52 PM, Prashanth N R via llvm-dev wrote: >> Hi- >> >> 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. >> >> 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. >> >> Entire code is in the spirit of LLVM. If the community is interested, we would like to work with the community and move forward. >> >> thanks, >> -Prashanth >> >> PS: We did try to use F18 for a while and hit the issues raised in [2], [3]. >> >> 1. http://lists.llvm.org/pipermail/llvm-dev/2019-August/134620.html <http://lists.llvm.org/pipermail/llvm-dev/2019-August/134620.html> >> 2. http://lists.llvm.org/pipermail/llvm-dev/2020-January/138069.html <http://lists.llvm.org/pipermail/llvm-dev/2020-January/138069.html> >> 3. http://lists.llvm.org/pipermail/flang-dev/attachments/20191202/6e7c1e51/attachment-0001.pdf <http://lists.llvm.org/pipermail/flang-dev/attachments/20191202/6e7c1e51/attachment-0001.pdf> >> OR http://lists.llvm.org/pipermail/flang-dev/2019-December/000089.html <http://lists.llvm.org/pipermail/flang-dev/2019-December/000089.html> >> >> >> >> _______________________________________________ >> LLVM Developers mailing list >> llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org> >> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev <https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev> > -- > Hal Finkel > Lead, Compiler Technology and Programming Languages > Leadership Computing Facility > Argonne National Laboratory > _______________________________________________ > LLVM Developers mailing list > llvm-dev at lists.llvm.org > https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20200112/06b28749/attachment.html>
Prashanth N R via llvm-dev
2020-Jan-13 07:43 UTC
[llvm-dev] FC : A MLIR+LLVM based Fortran front end
Hi Hal- In a day or two we will open source the code. Bigger clean up is expected by the end of this week. Of course the license will be LLVM license. thanks, -Prashanth On Sun, Jan 12, 2020 at 1:28 AM Finkel, Hal J. <hfinkel at anl.gov> wrote:> Hi, Prashanth, > > 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. > > -Hal > On 1/11/20 12:52 PM, Prashanth N R via llvm-dev wrote: > > Hi- > > 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. > > 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. > > Entire code is in the spirit of LLVM. If the community is interested, we > would like to work with the community and move forward. > > thanks, > -Prashanth > > PS: We did try to use F18 for a while and hit the issues raised in [2], > [3]. > > 1. http://lists.llvm.org/pipermail/llvm-dev/2019-August/134620.html > 2. http://lists.llvm.org/pipermail/llvm-dev/2020-January/138069.html > 3. > http://lists.llvm.org/pipermail/flang-dev/attachments/20191202/6e7c1e51/attachment-0001.pdf > OR http://lists.llvm.org/pipermail/flang-dev/2019-December/000089.html > > > _______________________________________________ > LLVM Developers mailing listllvm-dev at lists.llvm.orghttps://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev > > -- > Hal Finkel > Lead, Compiler Technology and Programming Languages > Leadership Computing Facility > Argonne National Laboratory > >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20200113/156f3c5d/attachment-0001.html>