[Bug middle-end/88897] Bogus maybe-uninitialized warning on class field (missed CSE)

2021-04-06 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88897 Martin Sebor changed: What|Removed |Added CC||msebor at gcc dot gnu.org Known to

[Bug middle-end/88897] Bogus maybe-uninitialized warning on class field

2019-01-22 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88897 Richard Biener changed: What|Removed |Added Keywords||missed-optimization

[Bug middle-end/88897] Bogus maybe-uninitialized warning on class field

2019-01-21 Thread rafael at espindo dot la
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88897 Rafael Avila de Espindola changed: What|Removed |Added CC||rguenther at suse dot de

[Bug middle-end/88897] Bogus maybe-uninitialized warning on class field

2019-01-20 Thread rafael at espindo dot la
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88897 Rafael Avila de Espindola changed: What|Removed |Added Attachment #45452|0 |1 is obsolete|

[Bug middle-end/88897] Bogus maybe-uninitialized warning on class field

2019-01-18 Thread rafael at espindo dot la
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88897 --- Comment #3 from Rafael Avila de Espindola --- (In reply to Andrew Pinski from comment #2) > Some of the time, the uninitialized is due to using the object after the > lifetime of the object has gone out of scope. I have not checked if that

[Bug middle-end/88897] Bogus maybe-uninitialized warning on class field

2019-01-17 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88897 --- Comment #2 from Andrew Pinski --- Some of the time, the uninitialized is due to using the object after the lifetime of the object has gone out of scope. I have not checked if that is the case here but I would not be suprised.