Hi, On Thu, 21 Jun 2012, Richard Guenther wrote:
> The flag is not restricted to the C++ compiler and applies to all > automatic variables. The use of that flag in the gimplifier (->in_cleanup_expr) makes it actually c++ specific. > Also even with this flag there is no guarantee we cannot figure out > lifetime in other ways, for example if the temporary gets promoted to a > register. Also with this patch you remove code motion barriers which > might cause other issues. > > A more "proper" place to fix this is when we actually do the stack > reuse, in cfgexpand. That is true, though. It would then also enable debugging help for pointers to things that go out-of-scope. Ciao, Michael.
