From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 298B03858D39; Thu, 29 Jun 2023 11:12:27 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 298B03858D39 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1688037147; bh=gfCFq/Kji6p5ChQwvTd2UWdyndi74NU02TUO0XVn45U=; h=From:To:Subject:Date:In-Reply-To:References:From; b=GHAgQtboVkmOAxnIkNHjXHH4Yh8Jn21X74xMITeknv4dOgiBVb7uvcnwN14xyR7+f sJOczdslCtGjd7akVjAphwaJYbARiJAQHZHEi73L3PBtkmy8SoPHq2EGTyAsCol9Ac QdXLnGv+f9QkP2J2xxnOgVp/TFiTCLn2afcpn768= From: "redi at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/110476] constexpr floating point regression with -std=c++XX Date: Thu, 29 Jun 2023 11:12:26 +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: redi 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=3D110476 --- Comment #3 from Jonathan Wakely --- I think the justification for GCC's behaviour is that "representable value"= is to be interpreted in the context of FLT_EVAL_METHOD, so it means representa= ble as double (for FLT_EVAL_METHOD=3D=3D1) or long double (for 2). "its type" is only mentioned in the first sentence, which doesn't apply to = IEEE types because they support infinities and so all values are in the range of representable values. The second sentence doesn't mention "its type".=