This meta-bug tracks SciMark 2.0 [1] performance issues. [1] http://math.nist.gov/scimark2/download_c.html
SciMark 2.0 has lots of tight loops that are ideal for perf. Just stating the benchmark score of two compilers does not represent a good report. We need at least a perf report, with eventual analysis of hot spots. Something similar to [1] is a good start. For regressions, a regression hunt like [2] is also welcome [1] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79389#c3 [2] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79389#c0
Please note that Phoronix SciMark 2.0 benchmark is faulty [1]. [1] https://kristerw.blogspot.si/2017/07/phoronix-scimark-benchmarking-results.html