On 11/01/2013 11:17 AM, Diego Novillo wrote:
On Fri, Nov 1, 2013 at 11:11 AM, Andrew MacLeod <amacl...@redhat.com> wrote:
Longer term... the BE will not be calling into gimplify at all.. it will be
purely a front end thing. As direct tree access vanishes, the optimizers
will be forced to generate gimple directly, as they should.
Right. Which is the routines in gimplify. I was under the impression
that you were proposing to move all the gimple generation routines to
gimplify. Or is it only the routines that convert FE trees to gimple?
If the latter, then my earlier suggestion makes no sense.
no, not moving anything/much to gimplify... the statement build
routines would be part of gimple-stmt since they build gimple-stmts.
gimplify would be routines that work on trees since that's what the
front end will present. And thats why the backend will no longer need
to gimplify anything... It'll just build stuff using the gimple-stmt
build and the gimple type/decl/expression building routines to come...
eventually :-).
