This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: [tree-ssa] Work around for an unfortunate fold-const vs.tree-optimizer interaction
- From: Diego Novillo <dnovillo at redhat dot com>
- To: Andrew Macleod <amacleod at redhat dot com>
- Cc: "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
- Date: Mon, 10 Nov 2003 16:22:56 -0500
- Subject: Re: [tree-ssa] Work around for an unfortunate fold-const vs.tree-optimizer interaction
- Organization: Red Hat Canada
- References: <Pine.LNX.4.44.0311061149050.12964-100000@www.eyesopen.com> <87vfpxcink.fsf@egil.codesourcery.com> <1068154239.7012.40.camel@p4>
On Thu, 2003-11-06 at 16:30, Andrew MacLeod wrote:
> Ona side note, Im about to turn GIMPLE back into GENERIC in
> SSA->normal, but only as far as expressions go... ie, allowing something
> more than a two operand expression. So we can get a string of
> assignments into temporaries that are only used once turned back into an
> expression. ie:
I was thinking today that perhaps we may want to think about moving the
tree->RTL expander to an earlier spot. What if instead of going into
normal form like we do now, we went directly from GIMPLE trees in SSA
form into RTL?
This would be a big change, for sure, but since all the data flow
information is there, in theory we would not need to combine trees nor
generate them in normal form.
It could also get unpleasantly ugly, though. Thoughts?
Diego.