[Bug regression/35671] GCC 4.4.x vs. 4.2.x performance regression
rguenth at gcc dot gnu dot org
gcc-bugzilla@gcc.gnu.org
Sat Aug 8 16:21:00 GMT 2009
------- Comment #19 from rguenth at gcc dot gnu dot org 2009-08-08 16:21 -------
Note that after a GCC version is released fixes for runtime regressions are
usually not considered because of their impact on stability (which is the
most important point). Instead if you care for performance of a specific
application (we _do_ monitor SPEC CPU 2000 and 2006 and some other benchmarks
and try to work hard to improve there) you should monitor performance of
your area of interest for the current development snapshots. Then there is
sufficient time to address regressions.
Note that usually a testcase and some analysis is still required - but at
least the likeliness that somebody will look and analyze the regression
for the development trunk is far more likely than for released versions.
Remember GCC is a volunteer driven project and benchmark analysis is
time-consuming.
At least both nbench and scimark are simple enough, so I'll add them to our
periodic monitoring of GCC trunk. (http://gcc.opensuse.org/)
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35671
More information about the Gcc-bugs
mailing list