https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69879
--- Comment #12 from Jonathan Wakely <redi at gcc dot gnu.org> --- Created attachment 47671 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47671&action=edit Elide exception handling in nothrow new Here's a proof of concept showing how to make the nothrow operator work without exceptions, and also give up if the new_handler keeps returning without making enough memory available. This avoids the overhead of throwing and catching bad_alloc, which is what I care about. Does this also adequately address the original concern? The (tries > 100) part should probably be user-controllable (maybe by a glibc-style tunable, see PR 88264).
