cache misses in gcc 3.3

[Geoff Keating]

Andi Kleen <ak@muc.de> writes:

> > One thing that is really important in going after speed improvements is
> > to have really accurate profiling information that shows where the time
> > is being spent. Otherwise you will chase phantoms.
> 
> My -O2 test case was spending 10% in the parser, according to the standard timing
> output. This was in the top three, with only CSE being slower. This was on an
> Athlon.

You should be aware that last time I looked, "parser" really meant
"all the time that wasn't allocated to some other part of the compiler".

-- 
- Geoffrey Keating <geoffk@geoffk.org>