http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38306
Richard Guenther <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |WORKSFORME
--- Comment #28 from Richard Guenther <rguenth at gcc dot gnu.org> 2012-01-16
12:38:17 UTC ---
Using original flags (-O3 -march=native -funroll-loops -ffast-math) on
a AMD Athlon(tm) 64 X2 (that's close enough to "Opteron") (same family 15):
4.2.4: 5.78s
4.3.6: 5.77s
4.4.6: 5.84s
4.5.3: 5.77s
4.6.2: 5.85s
trunk: 5.75s
seems to be a wash for me and I cannot reproduce even the originally
reported slowdown in 4.4. There are very many different flag measurements
in this report which makes it unlikely that this bug will be ever
properly triaged (or even "fixed").
Note that in general we'd like to concentrate monitoring performance
for standard flags (thus, not including -fschedule-insns if not enabled
by default). -Ofast -funroll-loops is a reasonable flag set, as we (still)
do not enable loop unrolling by default at -O3.
I'm closing this as worksforme. Please try to not make too much of a mess
out of regression bugreports ;)
