From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 2E0433849AD0; Fri, 3 May 2024 20:08:34 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 2E0433849AD0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1714766914; bh=OudWikBXMjDKVRi9Gfix8cx/mkqV6vu91ywKzyvwLyo=; h=From:To:Subject:Date:In-Reply-To:References:From; b=akOfuCD7j7eehJb4bdM4HzeNKkOZNHG8fOnyS8N/Kns8IA4arklnBjABx9qdk7cCJ aWD6OBmG9t3GNzcrtE+/iau8wNz7sJuskDOSZxh23drhAbrrSMf4t35uPBLTdwP00I Vvqftj2l54kbSRZ6t0HiGSxhWaJQ1GYRDSvmmR6w= From: "liuxf19 at 163 dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/114940] std::generator relies on an optional overload of operator delete Date: Fri, 03 May 2024 20:08:33 +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: 14.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: liuxf19 at 163 dot com 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=3D114940 --- Comment #4 from Timothy Liu Xuefeng --- (In reply to Jonathan Wakely from comment #2) > It's not optional, it's a required feature in C++14 and later. Failing to > provide it is non-conforming, although GCC can be requested to be > non-conforming the same way with -fno-sized-deallocation. Using that, the > same error happens with GCC. >=20 > We should either disable __cpp_lib_generator when __cpp_sized_deallocation > is not defined, or change to not depend on it unconditionally. Yeah, I agree. Since -fsized-deallocation is not the default behavior of clang++, reporting errors in seems strange.=