Over a month ago, I wrote , about SPEC2017:
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 cod
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 doi
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
s 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
&g
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
