public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug libstdc++/68210] nothrow operator fails to call default new
       [not found] <bug-68210-4@http.gcc.gnu.org/bugzilla/>
@ 2022-07-29 16:27 ` matthijs at stdin dot nl
  0 siblings, 0 replies; only message in thread
From: matthijs at stdin dot nl @ 2022-07-29 16:27 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68210

Matthijs Kooijman <matthijs at stdin dot nl> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |matthijs at stdin dot nl

--- Comment #8 from Matthijs Kooijman <matthijs at stdin dot nl> ---
Note that in comment:2, Jonathan Wakely pointed out a caveat:

> Also we certainly don't want to conform to the new requirement when
> libstdc++ is built with -fno-exceptions, because allocation failure
> would abort in operator new(size_t) and so the nothrow version never
> gets a chance to handle the exception and return null.

But this was not taken into account when implementing the fix for this issue,
meaning nothrow operators are now effectively useless with -fno-exceptions (and
there is thus no way to handle allocation failure other than aborting in that
case).

I created a new bug report about this here:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106477

^ permalink raw reply	[flat|nested] only message in thread
only message in thread, other threads:[~2022-07-29 16:27 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <bug-68210-4@http.gcc.gnu.org/bugzilla/>
2022-07-29 16:27 ` [Bug libstdc++/68210] nothrow operator fails to call default new matthijs at stdin dot nl

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).