https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113664
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2024-01-30
Status|UNCONFIRMED |NEW
Ever confirmed|0 |1
--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
Confirmed. As usual it's jump-threading related where we isolate, in the
-Warray-bounds case
MEM[(char *)1B] = 48;
we inline 'f' and then, when s == dot == NULL your code dereferences both
NULL and NULL + 1.
So the diagnostic messages leave a lot to be desired but in the end they
point to a problem in your code which is a guard against a NULL 's'.
The jump threading is different with -fwrapv-pointer, in particular without
it we just get the NULL dereference which we seem to ignore during
array-bound diagnostics.
We later isolate the paths as unreachable but that happens after the
diagnostic.
