From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 0EAF83858C5E; Mon, 10 Jul 2023 19:04:41 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 0EAF83858C5E DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1689015881; bh=WAkH8J8ouuNmRHkHS9mjroi575UB9OkdI+S1Snn1/oY=; h=From:To:Subject:Date:In-Reply-To:References:From; b=vL0eWJriUGymkAwKnnERDe5mbR8C7dVPNnO0csh0F/NyrddAO3eiBIaDW2smB+0f/ 59+om/ioCcqiPejN2XVrGXpZHwVBOFn+VQVH+gV8yy+mqpCtgkSfwQ6kCHh1v3VdcW d37MtNd+iFNPhPIFGXUXoZt2dEoIKnt0NgRNV6sk= From: "fchelnokov at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/110619] Dangling pointer returned from constexpr function converts in nullptr Date: Mon, 10 Jul 2023 19:04:40 +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: 13.1.0 X-Bugzilla-Keywords: diagnostic X-Bugzilla-Severity: normal X-Bugzilla-Who: fchelnokov at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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=3D110619 --- Comment #3 from Fedor Chelnokov --- I think according to https://eel.is/c++draft/basic.stc#general-4 the functi= on shall return an "invalid pointer valued". And nullptr is not considered suc= h. And if one modifies the function slightly (see auto p appear): constexpr auto g() { int i =3D 0; auto p =3D &i; return p; }; Then static_assert passes: https://gcc.godbolt.org/z/5shcxfcxG=