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 <tkoe...@netcologne.de> Sent: Sunday, October 6, 2019 10:53 AM To: Tamar Christina <tamar.christ...@arm.com>; gcc@gcc.gnu.org Cc: nd <n...@arm.com> 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?
