From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 47E82385841A; Mon, 20 Mar 2023 10:04:23 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 47E82385841A DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1679306663; bh=0n33Wc0Qet+SoOBJiaKP95g379pIg6Kv5XaEcVbyPqk=; h=From:To:Subject:Date:In-Reply-To:References:From; b=uLaQcv7fdB7uDtExZJTadV6PekeS1GZvrjNqsSJtF4KxU5YoVDt8yx5NYD0TPsH1a NQScugFrvYBfo8H9TmSwS0Ae++0ZGKCqJUGtJqtHR6GeTExrSTaOPNFqBrQWhvrp2i ZnxeTd1I+w/c60UlHv2AUWfNE1FTOE8Uuo/m39/0= From: "redi at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/93016] erroneous new (nothrow_t) still throws an exception Date: Mon, 20 Mar 2023 10:04:22 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 10.0 X-Bugzilla-Keywords: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: redi at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: DUPLICATE 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=3D93016 --- Comment #4 from Jonathan Wakely --- (In reply to Nikita Kniazev from comment #2) > This is a regression since GCC 6 https://godbolt.org/z/7WbYb9a7j Not really. The difference is that GCC 6 defaults to -std=3Dgnu++14 but if = you use that (or -std=3Dc++11) with GCC 5 you get the same behaviour.=