https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95663
Jeffrey A. Law <law at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |law at redhat dot com
--- Comment #10 from Jeffrey A. Law <law at redhat dot com> ---
trap is much stronger than an unreachable.
If you hit a gcc_unreachable location at runtime, execution just continues
onward with no indication something terrible has happened. It's literally just
a marker in our IL and results in no generated code. I think it's
fundamentally broken from a security standpoint.
__builtin_trap emits an actual trap into the instruction stream which halts the
process immediately which is *much* better from a security standpoint
