https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101953
Harald van Dijk <harald at gigawatt dot nl> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |harald at gigawatt dot nl
--- Comment #22 from Harald van Dijk <harald at gigawatt dot nl> ---
(In reply to M W from comment #3)
> If you think this is the correct behavior, remember, it is unexpected. At
> least give a warning when a value is set to zero instead of a faithful
> attempt to return the correct bits.
Agreed. Without special options, I think this behaviour is defensible,
undefined is undefined, but I would have expected -fsanitize=undefined to catch
this. clang's -fsanitize=undefined does catch this, gcc's doesn't (tested in
Ubuntu's version of GCC 10).
