From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 9CEB33858C2F; Mon, 20 Mar 2023 10:25:35 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 9CEB33858C2F DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1679307935; bh=sZvyFz+iDjT31nTwshE6Xlqil28IDxnltqZzHJRzBmc=; h=From:To:Subject:Date:In-Reply-To:References:From; b=FSLn0uwFCy/7smX5fNuqE//ps6PRJjktJ12xd65b4Gw4Jy+JrGA7j75HzmL9CMxWo W4S+dO5zHGIbYwxN5zFIKdv6JX43kJDc3oHRfmoIGZSV2msuUKcb94rNwWWekXVMMa UGRL3fmQJBgY6BvGhP3vs7CUTXXo1PnYGC/XRAzU= From: "redi at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/106477] With -fno-exception operator new(nothrow) aborts instead of returning null Date: Mon, 20 Mar 2023 10:25:34 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Version: 11.2.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: redi at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D106477 --- Comment #9 from Jonathan Wakely --- (In reply to Nikita Kniazev from comment #8) > bug 93016 might be related? Not really. This is about the behaviour of the library's operator new. In 9= 3016 the compiler should never even call the library function, because the new-expression is erroneous.=