https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99299
--- Comment #8 from Franz Sirl <sirl at gcc dot gnu.org> --- (In reply to Segher Boessenkool from comment #7) > (In reply to Franz Sirl from comment #5) > > For the naming I suggest __builtin_debugtrap() to align with clang. Maybe > > with an aliased __debugbreak() on Windows platforms. > > Those are terrible names. This would *not* be used more often than > __builtin_trap, for debugging. > > In general, builtins should say what they *do*, nott what you imagine they > will be used for. Let me re-phrase it. If the result of this discussion will result in a builtin that will be eqivalent to an "int 3" (or was it ud2? on x86) without "noreturn" as it is with clang, I would really prefer it to be called __builtin_debugtrap() even if the name is not great. Having different naming between GCC and clang seems worse to me.
