https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61721
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mpolacek at gcc dot gnu.org
--- Comment #6 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
(In reply to Lauri Kasanen from comment #5)
> A -fsanitize=undefined built binary does not print anything. I understand it
> can't catch all undefined behavior?
Correct.
> What is more interesting that adding -fsanitize=undefined to a failing case
> makes it work, changing nothing else. So it too affects the optimizer
> somehow.
It could be the case that added instrumentation code disabled some kind of
optimization that broke the behavior.
