[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gcc
Subject:    Re: cache misses in gcc 3.3
From:       Andi Kleen <ak () muc ! de>
Date:       2003-02-10 18:11:03
[Download RAW message or body]

On Mon, Feb 10, 2003 at 06:53:51PM +0100, Geoff Keating wrote:
> 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".

oprofile confirmed it - lots of hits in yyparse()

arguably that could be C code in the parser semantics too.

-Andi
[prev in list] [next in list] [prev in thread] [next in thread]