From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 062303858CDA; Mon, 10 Jul 2023 18:44:17 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 062303858CDA
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1689014657;
	bh=Q9q4212i14m2WLsF2+V9l2fwWcR3Mj9AdQzKk2tKGbg=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=tZ2sXCoHH6luLdfc8gR/qoY7aPY4mLmCGGrnfMJV4xpLxFTkOVNd/ArWHeDuiMv7s
	 96Zk/C9/E8GS0ExNQZMqQ1jekBIHkvl4kifZhEEJlm85XS01vOu4LwZev6YfcjGNkZ
	 a5n9iCZjEli+LwVpybNpiCxTmvyvxCPWLcbTe+8E=
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/110619] Dangling pointer returned from constexpr function
 converts in nullptr
Date: Mon, 10 Jul 2023 18:44:16 +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: pinskia at gcc dot gnu.org
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: <bug-110619-4-nNqR9n7aTs@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-110619-4@http.gcc.gnu.org/bugzilla/>
References: <bug-110619-4@http.gcc.gnu.org/bugzilla/>
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: <gcc-bugs.sourceware.org>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D110619

--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
>but it is not nullptr.

Or is it just undefined so it could be considered a nullptr ...=