https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78685
--- Comment #37 from Eric Gallager <egallager at gcc dot gnu.org> --- (In reply to Richard Sandiford from comment #36) > Regarding the subject change to add "it should generate artificial uses for > variables at end of scope to avoid this": I'm not sure that that's a > panacea. It would keep live the subset of assigned values that can reach > the end of the scope, and so would be better than the status quo, but it > wouldn't help with other assignments. > > Also, keeping the value live at the end of the scope guarantees that the > executable code can calculate the value at that particular point in the > program. It doesn't (IIUC) guarantee that a debugger can calculate the > correct value at all intermediate points, even with var-tracking. It's more > about increasing the chances. My purpose in retitling was primarily just to make the issue easier to find again, next time Jakub mentions it, since that's the solution he usually proposes.
