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



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.

Richard Henderson suggested we simply change the way we process the VAR_DECL's so that we walk the bind_vars before walking anything. That way, we don't have to move things around.



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