https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110437
--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> --- >With gcc 12.2 at least the same code doesn't trigger SIGILL. Well in GCC 13+ at -O0 and -Og, GCC behavior changed from being fully undefined to be trapping for folks to try to catch instead of saying they were seeing odd behavior. GCC 8+ changed the behavior to become unreachable: https://gcc.gnu.org/gcc-8/porting_to.html
