From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 28E5E3858433; Sat, 25 Feb 2023 23:15:12 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 28E5E3858433 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1677366912; bh=N/oPStLJYCRurbmqRRW0WSdDa1GY1R00sCyJ7/IME2k=; h=From:To:Subject:Date:In-Reply-To:References:From; b=yNoBBp8QLviiplvZQ2EnlvcHZ6mJIB90PPRAOX4b0eUcWl4Q8ODwkdY8RhHtou+SI CKYcV+4kFngKKe7GgkBaB0cBDyo6lCpzkYMS3GrSn5fZRkd+L7a10YKbfTy7gX6038 l9H6moIO31dVmFeKiabAx/ZEYz3NKgY2+X60NY1Y= From: "pinskia at gcc dot 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:15:11 +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: 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=3D108934 --- Comment #4 from Andrew Pinski --- Yes GCC 11.x produces wrong code too, remove constexpr from uint64_x_2_t_to= _ld and temp_uint64_x_2_t_to_ld to see that: uint64_x_2_t_to_ld: .long 1 .long 0 .long 0 .long 0 temp_uint64_x_2_t_to_ld: .long 1 .long 0 .long 0 .long 0=