https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79703
Uroš Bizjak <ubizjak at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |t.artem at mailcity dot com
--- Comment #1 from Uroš Bizjak <ubizjak at gmail dot com> ---
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
