https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78685
--- Comment #43 from Matthias Urlichs <matthias at urlichs dot de> --- On 12.03.26 09:51, rguenther at suse dot de wrote: > But making all variables > live until end of scope defeats the goal of having optimized code. True; however, maybe we can spend some effort on adapting the optimization rules here. My pet peeve here is that debuggable optimized code should free no-longer-used variables at the start of the next statement, instead of at the end of the current one. That way, I can set a conditional breakpoint on the result of a function call (i.e. on the next line) and would still be able to examine the call's arguments.
