public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "matthijs at stdin dot nl" <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: Fri, 29 Jul 2022 16:19:32 +0000 [thread overview] Message-ID: <bug-106477-4-0DchEYpJEC@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 #2 from Matthijs Kooijman <matthijs at stdin dot nl> --- Created attachment 53383 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53383&action=edit Testcase - startup code
next prev parent reply other threads:[~2022-07-29 16:19 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 [this message] 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 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-0DchEYpJEC@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).