https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95279
--- Comment #7 from Frantisek Sumsal <frantisek at sumsal dot cz> ---
Maybe I'm missing something here, but isn't detecting pointer overflows (even
in cases where it's apparently not an undefined behavior) the sole purpose of
-fsanitize=pointer-overflow (which, to my knowledge, is enabled by default when
using -fsanitize=undefined)?
As described in [0]:
-fsanitize=pointer-overflow
This option enables instrumentation of pointer arithmetics. If the pointer
arithmetics overflows, a run-time error is issued.
[0] https://gcc.gnu.org/onlinedocs/gcc/Instrumentation-Options.html
