https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120837
--- Comment #14 from Andrew Pinski <pinskia at gcc dot gnu.org> --- (In reply to Jakub Jelinek from comment #12) > Dunno if the best thing is to just drop this altogether, or don't do it for > -fsanitize=undefined, or do it but on pointer sized ints instead of pointers. I say remove/drop it for GCC 16 but disable it with -fsanitize=undefined for GCC 15/14/13/12. I suspect we would run into some aliasing issues too (I can't seem to find it right but `&a-1` causes the aliasing info here to point to nothing and things go down here from there).
