GCC trunk SPEC2000 performance

[Andreas Jaeger]

David Edelsohn <dje@watson.ibm.com> writes:

> 	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.

My pages contain the diffs between single runs so if somebody likes to
investigate...

> 2) "peak" (-O3 -funroll-all-loops -fprefetch=loop-arrays) produces slower
> code than base (-O2) for many tests.

And one more point: 301.apsi does not build on peak at all.

Andreas
-- 
 Andreas Jaeger
  SuSE Labs aj@suse.de
   private aj@arthur.inka.de
    http://www.suse.de/~aj