Shobaki, Ghassan via llvm-dev
2017-Sep-07 21:46 UTC
[llvm-dev] DragonEgg for GCC v8.x and LLVM v6.x is just able to work
> Out of curiosity, what is motivating this work? What is the usecase for dragonegg these days, now that Clang has great C++ support? Are you interested in Ada + LLVM or some other frontend? > > -ChrisWe are using Dragonegg in our academic research, because we are using SPEC CPU2006 for benchmarking. CPU2006 has many FP benchmarks written in Fortran, and this is still the case in CPU2017. Half of the FP benchmarks in CPU2017 have Fortran code. We are not particularly interested in Fortran, but I assume that this benchmark selection reflects the fact that a lot of important scientific programs are written in Fortran. We will be happy to use Flang as soon as it is ready and capable of compiling CPU2017. Our life will be much easier with a native Fortran front end. Ghassan Shobaki, Ph.D Assistant Professor of Computer Science California State University, Sacramento -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20170907/8a4ba834/attachment.html>
Hal Finkel via llvm-dev
2017-Sep-07 22:06 UTC
[llvm-dev] DragonEgg for GCC v8.x and LLVM v6.x is just able to work
On 09/07/2017 04:46 PM, Shobaki, Ghassan via llvm-dev wrote:> > Out of curiosity, what is motivating this work? What is the usecase > for dragonegg these days, now that Clang has great C++ support? Are > you interested in Ada + LLVM or some other frontend? > > > > -Chris > > We are using Dragonegg in our academic research, because we are using > SPEC CPU2006 for benchmarking. CPU2006 has many FP benchmarks written > in Fortran, and this is still the case in CPU2017. Half of the FP > benchmarks in CPU2017 have Fortran code. We are not particularly > interested in Fortran, but I assume that this benchmark selection > reflects the fact that a lot of important scientific programs are > written in Fortran. We will be happy to use Flang as soon as it is > ready and capable of compiling CPU2017. Our life will be much easier > with a native Fortran front end. >I believe that it can now. You should go to flang-compiler.org and, if you find a problem, please file an issue on the flang github page. -Hal> > > Ghassan Shobaki, Ph.D > > Assistant Professor of Computer Science > > California State University, Sacramento > > > > _______________________________________________ > LLVM Developers mailing list > llvm-dev at lists.llvm.org > http://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/20170907/dfccd62d/attachment.html>
Das, Dibyendu via llvm-dev
2017-Sep-08 03:12 UTC
[llvm-dev] DragonEgg for GCC v8.x and LLVM v6.x is just able to work
Flang should be able to compile most of CPU2017 if not all of them. From: llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org] On Behalf Of Shobaki, Ghassan via llvm-dev Sent: Friday, September 08, 2017 3:17 AM To: llvm-dev at lists.llvm.org Subject: Re: [llvm-dev] DragonEgg for GCC v8.x and LLVM v6.x is just able to work> Out of curiosity, what is motivating this work? What is the usecase for dragonegg these days, now that Clang has great C++ support? Are you interested in Ada + LLVM or some other frontend? > > -ChrisWe are using Dragonegg in our academic research, because we are using SPEC CPU2006 for benchmarking. CPU2006 has many FP benchmarks written in Fortran, and this is still the case in CPU2017. Half of the FP benchmarks in CPU2017 have Fortran code. We are not particularly interested in Fortran, but I assume that this benchmark selection reflects the fact that a lot of important scientific programs are written in Fortran. We will be happy to use Flang as soon as it is ready and capable of compiling CPU2017. Our life will be much easier with a native Fortran front end. Ghassan Shobaki, Ph.D Assistant Professor of Computer Science California State University, Sacramento -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20170908/69deca90/attachment.html>