https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93432
Vincent Lefèvre changed:
What|Removed |Added
CC||vincent-gcc at vinc17 dot net
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93432
Manuel López-Ibáñez changed:
What|Removed |Added
Keywords||easyhack
--- Comment #5 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93432
Manuel López-Ibáñez changed:
What|Removed |Added
CC||manu at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93432
--- Comment #3 from Sven ---
I'm not sure how you optimize the uninit use away. When running the example,
the first printf typically yields a random value. So the uninitialized value is
certainly used as a return value.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93432
--- Comment #2 from Richard Biener ---
The one involving constants and PHIs. The (late) uninit warning is too late to
catch this since we optimized the uninit use away. We probably diagnose
it if you initialize z from a function parameter
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93432
Martin Liška changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93432
Eric Gallager changed:
What|Removed |Added
Keywords||diagnostic
CC|
