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: COND_EXPRs in GIMPLE code and vectorizer


Roberto COSTA wrote on 09/28/06 05:51:

> If time allows me, I'd like to try to see what happens if COND_EXPRs are 
> kept throughout the GIMPLE passes (I confess I'm curious). Logically, I 
> see them as richer constructs (they carry more information than the 
> equivalent control-flow code), like MIN_EXPRs and MAX_EXPRs.
>
Be wary of VRP and thread jumping if you do this.  Both rely on the
current COND_EXPR format quite heavily.

> What do you mean by "tree combiner"?
> 
A pass that combines two or more GIMPLE statements into a single GIMPLE
statement.  At least one effort started down this path but was never
completed.


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