https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114080
--- Comment #7 from Andrew Pinski <pinskia at gcc dot gnu.org> --- (In reply to Chris Rapier from comment #5) > So what you are saying is that behaviour *has* changed and what was a valid > operation for 15 years is now invalid. I'm not mad about that. I just needed > to know. behavior didn't change, it was always undefined. -fsanitize=undefined has been catching it almost for the last 10 years (since r5-2363-g944fa280bc92d1).