https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89035
Eric Gallager changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89035
Eric Gallager changed:
What|Removed |Added
CC||egallager at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89035
Martin Sebor changed:
What|Removed |Added
CC||msebor at gcc dot gnu.org
--- Comment #3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89035
--- Comment #2 from David Brown ---
Yes, "int x = x;" does give an unspecified value without a warning. But to me,
this looks much more like a workaround - while "int x =
__builtin_unspecified();" is clear in its intentions.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89035
--- Comment #1 from Marc Glisse ---
We already have
int x = x;
for one of those, no? Or just
int x;
but it tends to warn.
