BBRO on non-pipelined processors - bad?

tm tm@mail.kloo.net
Tue Oct 22 11:36:00 GMT 2002


On Tue, 22 Oct 2002, Richard Henderson wrote:

> On Fri, Oct 18, 2002 at 04:26:04PM -0700, tm wrote:
> > I'd like to create a target macro defined something like:
> > 
> > #define CONSTANT_CYCLE_BRANCH 1
> > 
> > ...and then we can do in toplev.c:
> > 
> > #ifdef CACHE_LOG
> > 	if (!CONSTANT_CYCLE_BRANCH || CACHE_LOG)) {
> > 		(call bbro here)
> > 	}
> > #endif
> > 
> > Is this acceptable?
> 
> No.  Use OPTIMIZATION_OPTIONS.
> 
> 
> r~

Putting this feature in OPTIMIZATION_OPTIONS seems kinda kludgy
(same as disabling bbro in target.c) because there are probably
several other embedded processors/DSPs which can benefit from this:

dsp16xx
mn10200
mn10300
stormy16
v850

I'll try to submit a patch shortly, in either case.

Toshi




More information about the Gcc-bugs mailing list