https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104642
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> --- Not sure, people will still see the surprising behavior at -O1+ then and at -O0 we're not exploiting the __builtin_unreachable () in too surprising ways (we'll just fall thru to the next function or so - heh. I'd rather have -funreachable-traps or so, enabled by default at -O0, rather than special-casing the return case btw.
