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 c++/99934] bad_array_new_length thrown when non-throwing allocation function would have been used Date: Mon, 20 Mar 2023 10:23:53 +0000 [thread overview] Message-ID: <bug-99934-4-nUxz26Dj7r@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99934-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99934 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed|2022-03-28 00:00:00 |2023-3-20 --- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> --- Another case from Bug 102514: namespace std { using size_t = decltype(sizeof(0)); } extern "C" void abort(); extern "C" int puts(const char*); int main() { int n = -1; struct C { void* operator new[](std::size_t n) noexcept(false) { puts("C::operator new[] called"); abort(); } }; C* ptr = new C[n]; } C::operator new[] called Aborted (core dumped) I guess we don't throw bad_array_new_length here because sizeof(C) * size_t(-1) fits in size_t. But it's still larger than the maximum possible object size, and in any case, the expression n is less than zero so is erroneous so operator new should never be called. The compiler should throw bad_array_new_length. Similarly for this one with a non-throwing operator new[]: namespace std { using size_t = decltype(sizeof(0)); } extern "C" void abort(); extern "C" int puts(const char*); int main() { int n = -1; struct C2 { void* operator new[](std::size_t n) noexcept(true) { puts("C2::operator new[] called"); abort(); } }; C2* ptr = new C2[n]; } The sizeof(C2) * size_t(-1) result fits in size_t, so G++ calls the operator new[]. But the expression is still erroneous, and so the compiler should just produce a null pointer without calling C2::operator new[].
next prev parent reply other threads:[~2023-03-20 10:23 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-06 11:33 [Bug c++/99934] New: " redi at gcc dot gnu.org 2021-04-06 12:41 ` [Bug c++/99934] " jakub at gcc dot gnu.org 2022-03-28 9:17 ` redi at gcc dot gnu.org 2023-03-20 9:52 ` redi at gcc dot gnu.org 2023-03-20 10:08 ` redi at gcc dot gnu.org 2023-03-20 10:23 ` redi at gcc dot gnu.org [this message] 2024-04-22 16:14 ` 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-99934-4-nUxz26Dj7r@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).