https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89035
--- Comment #2 from David Brown <david at westcontrol dot com> --- 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.
