This is the mail archive of the 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] where to fix this?

In message <>, Jan Hubicka writes:
 >I don't think the idea of actually doing the folding and then testing
 >whether it is valid is good.  It costs memory and folder may get to be
 >over-active stepping out of allowed ground missing allowed
 >transformation as commonly happens for combine.
There's certainly times when I'm going to want to give fold a fairly
complex expression, but I'm going to want to know if the result of folding
that complex non-gimple expression results in a gimple expression.  That
can either be done in all the callers or it can be controlled by passing
a flag/callback to the folder.

Given that we already have a couple places where we need this, I'd prefer
to have this behavior in the folder itself, controlled by the caller setting
the right flag and/or callback.

 >Also how callback "it is valid transformation according to C standard"
 >can be implemented?  It still has to know all the transformations C
 >standard mention.
The callback is set up by the front-end to call a front-end routine.


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