[Bug c++/58455] spurious "may be used uninitialized" warning with -Og

[law at redhat dot com]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58455

Jeffrey A. Law <law at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |law at redhat dot com
             Blocks|                            |19794

--- Comment #7 from Jeffrey A. Law <law at redhat dot com> ---
I've long pondered separating jump threading from DOM and making jump threading
a backwards walk of the use-def chains from the condition.

Given such a structure one could envision a knob which controlled how far back
in the use-def chains we walk.  If that knob just allowed walking one
statement, we'd catch the jump threads in blocks #4 and #7 trivially.

But that's all work far into the future.

Of course that still leaves an open question about what, if any threading we'd
want to do at -Og.  We'd certainly have to look at that closely.