This is the mail archive of the gcc-patches@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: PR 23551: why should we coalesce inlined variables?


On 7/8/07, Alexandre Oliva <aoliva@redhat.com> wrote:
On Jul 7, 2007, Jan Hubicka <hubicka@ucw.cz> wrote:

>> On Jun 28, 2007, Andrew MacLeod <amacleod@redhat.com> wrote:
>>


That said, maybe with the work I have in mind we'll be able to enable coalescing for all user variables (not only those coming from inlined functions), and retain the annotations needed to map the assignments back to user variables somehow. However, I'm not convinced yet that it can be done in a way that consumes less memory, basically because we'd have to keep track of which variables map to which assignments to SSA variables, and this would amount to further SSA analysis and assignments, or annotations that would have to be dealt with in a very similar way. That said, ideas are welcome.

This looks like a standard propagation problem you could use tree-ssa-propagate to solve, generate the mapping, output debugging info, and throw away the mapping.


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