https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118717
--- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> --- (In reply to Sam James from comment #5) > fwiw this showed up when I started to force using `setjmp` instead of > `__builtin_setjmp` in ruby a few days ago. I haven't looked at how (if at > all) we treat those differently because on mobile Well __builtin_setjmp should be treated as return twice but maybe it is not exactly. Anyways __builtin_setjmp should really not be used as it is not equal to setjmp which is why I assume you were forcing to use setjmp instead.