public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/106477] With -fno-exception operator new(nothrow) aborts instead of returning null Date: Sun, 15 Jan 2023 22:53:17 +0000 [thread overview] Message-ID: <bug-106477-4-58o8Krcpip@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106477-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106477 --- Comment #7 from Jonathan Wakely <redi at gcc dot gnu.org> --- (In reply to Matthijs Kooijman from comment #6) > Ah, IIUC your patch does not treat -fno-exceptions specially, but just adds > a shortcut for the nothrow new version to skip calling regular new version > if it has not been replaced. In a normal build, that saves throw/catch > overhead, and in a no-exceptions build that prevents the abort associated > with that throw. Clever! Right. > One corner case seems to be when the regular new version is replaced in a > no-exceptions build, but in that case that replacement has no way to signal > failure anyway, and if needed a user can just also replace the nothrow > version. If the regular version has been replaced, we have to call it (and handle possible exceptions) because we can't know what it does, so calling malloc directly would not be safe. So yes, users who want to replace new but don't want exceptions involved in the nothrow new path just need to replace both forms. That's true already today, and my patch wouldn't change it.
next prev parent reply other threads:[~2023-01-15 22:53 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-29 16:18 [Bug libstdc++/106477] New: " matthijs at stdin dot nl 2022-07-29 16:18 ` [Bug libstdc++/106477] " matthijs at stdin dot nl 2022-07-29 16:19 ` matthijs at stdin dot nl 2022-07-29 16:20 ` matthijs at stdin dot nl 2022-07-29 16:41 ` redi at gcc dot gnu.org 2022-12-14 13:16 ` redi at gcc dot gnu.org 2023-01-15 18:56 ` matthijs at stdin dot nl 2023-01-15 22:53 ` redi at gcc dot gnu.org [this message] 2023-03-19 21:51 ` nok.raven at gmail dot com 2023-03-20 10:25 ` redi at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-106477-4-58o8Krcpip@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
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).