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

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58377 Bug 58377 depends on bug 58402, which changed state. Bug 58402 Summary: [4.9 regression] FAIL: gcc.dg/tree-ssa/phi-opt-1.c scan-tree-dump-times optimized "if" 0 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58402 What|Removed

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

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58377 Richard Biener changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

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

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58377 --- Comment #13 from Richard Biener --- Author: rguenth Date: Wed Sep 11 12:23:15 2013 New Revision: 202498 URL: http://gcc.gnu.org/viewcvs?rev=202498&root=gcc&view=rev Log: 2013-09-11 Richard Biener PR middle-end/58377 * passes.c (in

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

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58377 --- Comment #12 from Richard Biener --- Author: rguenth Date: Wed Sep 11 12:20:07 2013 New Revision: 202496 URL: http://gcc.gnu.org/viewcvs?rev=202496&root=gcc&view=rev Log: 2013-09-11 Richard Biener PR middle-end/58377 * passes.def:

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

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58377 --- Comment #11 from Richard Biener --- (In reply to davidxl from comment #10) > When an incoming edge to a phi is a critical edge, the 'use BB' for the phi > arg should be in the split BB of the edge. Pushing the use into either the > Source BB

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

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58377 --- Comment #10 from davidxl at google dot com --- When an incoming edge to a phi is a critical edge, the 'use BB' for the phi arg should be in the split BB of the edge. Pushing the use into either the Source BB or the dest BB will result in exte

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

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58377 --- Comment #9 from davidxl at google dot com --- (In reply to Richard Biener from comment #5) > Confirmed with the C++ FE, works with the C FE. Does not warn on trunk (for > no good reason I think, the reason seems to be presence of loop structur

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

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58377 --- Comment #8 from davidxl at google dot com --- (In reply to Neil Vachharajani from comment #7) > It seems like the whole problem is that the loop early exit goes through > bb_6 which is the same path the back-edge goes through. There is also on

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

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58377 Neil Vachharajani changed: What|Removed |Added CC||nvachhar at google dot com --- Commen

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

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58377 davidxl at google dot com changed: What|Removed |Added CC||davidxl at google dot com ---