https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78822
--- Comment #20 from Pedro Alves <palves at redhat dot com> --- And in addition, since GCC is already using new/new[] to heap allocate its own classes, GCC is _already_ inconsistent with allocation failure -- if one of those currently fails, you'll end up with a C++ exception that nobody is catching, so GCC dies a horrible death. Replacing operator new of course would handle those too.
