Compilation time

[Jan Hubicka]

> Benjamin Kosnik <bkoz@redhat.com> writes:
> 
> > I agree, since speed has been swept under the rug for the 3.0.x, 3.1.x,
> > and 3.2.x releases, it might be nice to address it in a direct manner.
> > Matt, part of doing this might be getting the Apple regression tester to
> > actually spit out time data (even for things like bootstrap, and
> > individual timings of each language test run). That might make the speed
> > issue more visible.
> 
> This is already done by mine (and I think also by Diego's) SPEC
> testers.  Both bootstrap time and compile time of the programs are
> tracked, e.g. for mainline:
> http://www.suse.de/%7Eaj/SPEC/CINT/d-permanent/times.html

Unforutnately the noise in benchmarks is high enought to hide the actual
changes - one can see the line going up but not the individual jumps.  I
am not sure whether this can be avoided.  We are speaking about
cumulative effect of many patches each causing slowdown smaller than 1%.

Honza
> 
> Andreas
> 
> P.S.: My testers are finally up again.
> -- 
>  Andreas Jaeger
>   SuSE Labs aj@suse.de
>    private aj@arthur.inka.de
>     http://www.suse.de/~aj