This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Compile-time and execution-time impact of CSE - some numbers

From: Paolo Bonzini <paolo dot bonzini at polimi dot it>
To: Steven Bosscher <stevenb at suse dot de>
Cc: gcc at gcc dot gnu dot org
Date: Tue, 31 Aug 2004 22:53:52 +0200
Subject: Re: Compile-time and execution-time impact of CSE - some numbers
References: <1093958955.41347d2b7d59f@webmail.polimi.it> <200408311550.27667.stevenb@suse.de>

> The second step would be to
> make cse.c use the CFG (ie. FOR_BB_INSNS/BB_HEAD/BB_ END/etc.) instead
> of relying on block notes.

Block notes are the lesser problem.  It's using barriers and labels to detect 
edge types, that would drive me nuts :-)

> Next you'd clean up the path following code
> to track back only to the last visited block before following a jump.

Is it different from a very low --param max-cse-path-length?

Paolo

-------------------------------------------------
This mail sent through IMP: http://horde.org/imp/

References:
- Compile-time and execution-time impact of CSE - some numbers
  - From: Paolo Bonzini
- Re: Compile-time and execution-time impact of CSE - some numbers
  - From: Steven Bosscher

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]