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: [tree-ssa] Fix variables getting out of their scope



On Wednesday, August 20, 2003, at 6:20 PM, Daniel Berlin wrote:



Except, when you move a statement, doesn't it's scope change? We don't reset it to the right scope automatically, do we? So stmt_ann (stmt)->scope will be the wrong scope still (and scope_level will be off)

ah, sure.


I have to do something like this hack (which only works if there are
other statements in the block you are moving to), methinks:

well, almost. Given that boundary of BIND_EXPR may be in the middle of
a basic block, this does not always have to be exactly what you want.
Not that I would be aware of an easy solution.


Also, the code i posted bootstraps with LICM enabled on every platform i could find, as well as passing all regression tests. So it looks like it's "good enough" until we come up with a better solution and implement it.



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