https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109565
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2023-04-20
Ever confirmed|0 |1
--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
-Wstrict-overflow is hardly ever useful - it diagnoses cases where GCC
performs a simplification that's valid because overflow invokes undefined
behavior (but it doesn't actually try to prove overflow will or will not
happen). We've been slowly ripping out most of those diagnostics.
You're supposed to use -fsanitize=undefined instead which will diagnose
cases where actual overflow happens at runtime (so it's not exhaustive
either).
