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: [tree-ssa] Use of build_binary_op

On Thu, Sep 26, 2002 at 01:30:17PM +0200, Steven Bosscher wrote:
> 
> I'm not suggesting you optimize each statement. I'm suggesting we just
> leave it to the front end to decide where break/goto elimination (or
> some other transformation) is appropriate. The front end knows much
> better when such a transformation is useful.

Then on the top-level we could allow the front-end to order all the 
optimizations that doesn't interfere with others.  I guess that these 
optimizations are either GENERIC to GENERIC or GIMPLE to GIMPLE.

For example 

inline: GENERIC -> GENERIC
jump_opt: GIMPLE -> GIMPLE
...
Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]