public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "keith.halligan at microfocus dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/99845] gcc8: Overloaded operator new[](size_t, const std::nothrow_t&) is seg faulting when the allocation fails Date: Tue, 06 Apr 2021 07:35:45 +0000 [thread overview] Message-ID: <bug-99845-4-gVYUM3Yvfx@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99845-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99845 Keith Halligan <keith.halligan at microfocus dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID |--- --- Comment #11 from Keith Halligan <keith.halligan at microfocus dot com> --- I am re-opening this issue as there seems to be a bug with the 32-bit code generation that I'm after noticing. While adding noexcept to the "opeator new[]()" overloaded functions does stop the crash on 64-bit, it does nothing for the 32-bit code, with the compiler attempting to throw a std::bad_alloc. Below is a version of Jonathan Wakeley's modified testcase that has noexcept on the "operator new[]()". $ cat bug99845.cpp && g++ -m32 -O1 -o bug99845 bug99845.cpp namespace std { using size_t = decltype(sizeof(0)); struct nothrow_t { } const nothrow = { }; } void* operator new(std::size_t); void* operator new[](std::size_t); void operator delete(void*) noexcept; void operator delete[](void*) noexcept; void operator delete(void*, std::size_t) noexcept; void operator delete[](void*, std::size_t) noexcept; void* operator new(std::size_t, const std::nothrow_t&) noexcept; void* operator new[](std::size_t, const std::nothrow_t&) noexcept; void operator delete(void*, const std::nothrow_t&) noexcept; void operator delete[](void*, const std::nothrow_t&) noexcept; extern "C" int printf(const char* ...); using std::size_t; struct X { void* operator new[](size_t sz, const std::nothrow_t& nt) noexcept { return ::operator new(sz, nt); } unsigned data = 0; }; struct Y { static X* alloc(unsigned n) { return new(std::nothrow) X[n]; } }; int main() { Y::alloc(-1u); } == $ ./bug99845 terminate called after throwing an instance of 'std::bad_array_new_length' what(): std::bad_array_new_length Aborted (core dumped)
next prev parent reply other threads:[~2021-04-06 7:35 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-31 9:00 [Bug c++/99845] New: " keith.halligan at microfocus dot com 2021-03-31 9:40 ` [Bug c++/99845] " rguenth at gcc dot gnu.org 2021-03-31 9:46 ` jakub at gcc dot gnu.org 2021-03-31 9:50 ` rguenth at gcc dot gnu.org 2021-03-31 10:47 ` redi at gcc dot gnu.org 2021-03-31 11:40 ` redi at gcc dot gnu.org 2021-03-31 11:52 ` redi at gcc dot gnu.org 2021-03-31 11:53 ` redi at gcc dot gnu.org 2021-03-31 12:02 ` redi at gcc dot gnu.org 2021-03-31 16:36 ` msebor at gcc dot gnu.org 2021-03-31 17:23 ` redi at gcc dot gnu.org 2021-04-06 7:35 ` keith.halligan at microfocus dot com [this message] 2021-04-06 11:35 ` 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-99845-4-gVYUM3Yvfx@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).