GCC trunk SPEC2000 performance
David Edelsohn
dje@watson.ibm.com
Wed Jun 19 21:26:00 GMT 2002
To avoid the argument that GCC 3.2 performance regressions were
reported too late in the release cycle, does anyone know why the graphs on
Andreas Jaeger's SPEC CPU2000 performance tracking page show:
1) 181.mcf, 254.gap, 172.mgrid, performance has fallen precipitously. The
trunk produces worse code than GCC 2.95, 3.0, and 3.1.
2) "peak" (-O3 -funroll-all-loops -fprefetch=loop-arrays) produces slower
code than base (-O2) for many tests.
David
More information about the Gcc
mailing list