GCC Spec2017 optimization Wiki
Hi All, As discussed during the Cauldron I have created a wiki page https://gcc.gnu.org/wiki/GCCSpec2017 For us to discuss and exchange ideas to improve GCC's spec score. I have created pages for all the benchmarks and have filled in an analysis for MCF https://gcc.gnu.org/wiki/GCCSpec2017/mcf We will be filling in these pages as we go along but I encourage you if you have an analysis or comments to do chime in! Thanks, Tamar
Re: GCC Spec2017 optimization Wiki
Am 06.10.19 um 16:25 schrieb Tamar Christina: As discussed during the Cauldron I have created a wiki page https://gcc.gnu.org/wiki/GCCSpec2017 For us to discuss and exchange ideas to improve GCC's spec score. A few of them are written in Fortran. As SPEC is closed source and costs are quite high, none of the gfortran maintainers (who are all volunteers) is in a position to contribute. Any ideas how to do anything about that?
RE: GCC Spec2017 optimization Wiki
Hi Thomas, In general our approach is to identify areas for improvement in a benchmark and provide a testcase that's independent of the benchmark when reporting it in a PR upstream. This simplifies the problem and also allows people who don't have access to SPEC to contribute. Of course this is not always do-able but for a large part of the cases so far this has worked out well. So I think that's the best way to handle the Fortran and other benchmarks. For the bigger work items we may need to find an alternative. Cheers, Tamar -Original Message- From: Thomas Koenig Sent: Sunday, October 6, 2019 10:53 AM To: Tamar Christina ; gcc@gcc.gnu.org Cc: nd Subject: Re: GCC Spec2017 optimization Wiki Am 06.10.19 um 16:25 schrieb Tamar Christina: > As discussed during the Cauldron I have created a wiki page > https://gcc.gnu.org/wiki/GCCSpec2017 > For us to discuss and exchange ideas to improve GCC's spec score. A few of them are written in Fortran. As SPEC is closed source and costs are quite high, none of the gfortran maintainers (who are all volunteers) is in a position to contribute. Any ideas how to do anything about that?
Re: GCC Spec2017 optimization Wiki
Hi Tamar, In general our approach is to identify areas for improvement in a benchmark and provide a testcase that's independent of the benchmark when reporting it in a PR upstream. Sounds like a good approach, in principle. If the people who are doing the identfying know Fortran well, that would work even better (do they?), and if they could be persuaded to work on gfortran directly, that would probably be best. Regards Thomas
Re: GCC Spec2017 optimization Wiki
On 10/6/19 5:14 PM, Thomas Koenig wrote: Hi Tamar, In general our approach is to identify areas for improvement in a benchmark and provide a testcase that's independent of the benchmark when reporting it in a PR upstream. Sounds like a good approach, in principle. If the people who are doing the identfying know Fortran well, that would work even better (do they?), and if they could be persuaded to work on gfortran directly, that would probably be best. Of the 7 benchmarks that are (partly) written in Fortran, Cactus is free software (LGPL'd) and the 3 geological ones (wrf, cam4 and roms) are "obtainable" (need to register to get the source code). Of course, that means you get "a" version of the code, not necessarily what is in the SPEC benchmark, but at least it enables us to join in the analysis. exchange2 was written by Michael Metcalf, of countless Fortran books, whom I met once (when I was on the Fortran Standardization Committee). He might be persuaded to give us a copy for analysis if this really is an outlier in performance. Kind regards, -- Toon Moene - e-mail: t...@moene.org - phone: +31 346 214290 Saturnushof 14, 3738 XG Maartensdijk, The Netherlands At home: http://moene.org/~toon/; weather: http://moene.org/~hirlam/ Progress of GNU Fortran: http://gcc.gnu.org/wiki/GFortran#news
gcc-10-20191006 is now available
Snapshot gcc-10-20191006 is now available on ftp://gcc.gnu.org/pub/gcc/snapshots/10-20191006/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 10 SVN branch with the following options: svn://gcc.gnu.org/svn/gcc/trunk revision 276640 You'll find: gcc-10-20191006.tar.xz Complete GCC SHA256=c31be703d1105a69d40b169da2eaee9553309b3114913c4f71ae157c892f70ce SHA1=54265ef4656a140b33b087bb11e38188c6b0950f Diffs from 10-20190929 are available in the diffs/ subdirectory. When a particular snapshot is ready for public consumption the LATEST-10 link is updated and a message is sent to the gcc list. Please do not use a snapshot before it has been announced that way.
