https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87952
Thiago Macieira <thiago at kde dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |thiago at kde dot org
--- Comment #4 from Thiago Macieira <thiago at kde dot org> ---
> Could you please elaborate on what you mean by "might end up as a security
> issue"?
I don't see it either. Crashing with the UD2 instruction (SIGILL) or via
null-pointer dereference (SIGSEGV) is functionally the same: the application
stops. If Richard meant that GCC could instrument in some build modes to
provide a different diagnostic, then I'd say that it should keep the branch
only if such code exists. If the code is going to hit a crashing signal either
way, opt for the branchless and shorter version.
