From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 74DE43861002; Wed, 28 Aug 2024 09:08:39 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 74DE43861002 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1724836119; bh=wR92pHfMqqK6nhHA8V+U90KPE6h3qjWHn/eCx4272bM=; h=From:To:Subject:Date:In-Reply-To:References:From; b=o32TR+7qiljEjHIwep5CiHb6yXEuf2aFV/coiF1ZsgSsC8fTTmGjVdzmbL3bAspEc GEQmTzAALYyAE338dxZhqUaL5hMGKx5ha/i0IU1QC7Q3f++mjaAQ/eMJnBcN/2ZQxY AJA9Po26CVptixu/1RZHjs1t8vODtt8ldwQIOFJ4= From: "redi at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/116473] Better diagnostic for dynamic allocation that isn't freed by constant expression Date: Wed, 28 Aug 2024 09:08: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: 14.1.0 X-Bugzilla-Keywords: diagnostic 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: everconfirmed bug_status cf_reconfirmed_on keywords short_desc 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=3D116473 Jonathan Wakely changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |NEW Last reconfirmed| |2024-08-28 Keywords|rejects-valid |diagnostic Summary|std::ranges::to vs |Better diagnostic for |constexpr |dynamic allocation that | |isn't freed by constant | |expression --- Comment #2 from Jonathan Wakely --- Agreed. But maybe we could improve the "because it refers to a result of operator new" diagnostic. The problem isn't that the pipeline expression refers to the result of oper= ator new, it's that it doesn't deallocate it before the end of the constant expression.=