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 4D2263858433; Sat, 25 Feb 2023 23:11:31 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 4D2263858433
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1677366691;
	bh=VNnr9O51WzsgVBbqhbmIPYC9ErlcRK+TXagRTgMAkMo=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=efNo4pIC78sB+Ig8qKVcuYd627OYXXNOKWyPjAzROEhU7gOlnxDk6B43iXl7r74sJ
	 YboDVMAQOSUlFEZxah/mcD2fwfYGB5uXKRKCRFe+4lktIs4uNyOreBtNqK+B3AwkVV
	 7VIz8gydqm5em1Lu9RqhdL3WA7KL2sPj8DNVHC4A=
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/108934] bit_cast'ing to long double errors out with "the
 argument cannot be interpreted" since gcc-12
Date: Sat, 25 Feb 2023 23:11:31 +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.0
X-Bugzilla-Keywords: 
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: cf_gcctarget
Message-ID: <bug-108934-4-9TUpsXjFcX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-108934-4@http.gcc.gnu.org/bugzilla/>
References: <bug-108934-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=3D108934

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Target|                            |x86_64

--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
That is doing {0u, 0u} works too.
And even {1u, 0u}; does too.=