From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id C45FA385842E; Thu, 29 Jun 2023 08:03:36 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C45FA385842E DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1688025816; bh=t+UB6b2hnmT2meUie0j+7tGQOzB25ZOsFzffldw6UTw=; h=From:To:Subject:Date:In-Reply-To:References:From; b=dFkloAfymvEXaCvf/OC7nswXYQScBiEJTPh0R0HqjhTViVieU0Mu/yr7BCwHetQoI hNeTPq6GlwAGNDGqVvgbs7nYtpMFQ608acRkA43WJ+iOCJTB2WbB0VNcjthCl8tcrZ S9o3It7Xlyfx5bTb8OV35pszdlyFTi9yJoaVoAZE= From: "pdimov at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/110476] constexpr floating point regression with -std=c++XX Date: Thu, 29 Jun 2023 08:03:36 +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: X-Bugzilla-Severity: normal X-Bugzilla-Who: pdimov 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=3D110476 --- Comment #1 from Peter Dimov --- As discussed in https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D108742, this= is a consequence of applying the FLT_EVAL_METHOD=3D2 rules, and can be fixed by casting 3.14f to (float). That's... incredibly surprising, though. 3.14f is already a float. For context, I encountered this regression in the Boost.Variant2 test suite when I added GCC 13 to CI.=