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 E168F3858C2D; Tue, 27 Sep 2022 08:59:34 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org E168F3858C2D
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1664269174;
	bh=rU1AZ5RYDzmx26I/+JDcPL5vyXmoMDej1f+Ipkk33JM=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=La0pgi0P/iUo8/xHM5E27ICYJyHoorMegl9BWh4OGPBWjnFGvPG4UlMcOB0TT2lDG
	 sSsYYr+NeFwZId2M1DoJ/3GfMUmjDebZA5OZ9oOpcvM6AG29DTYWqwEmxzLtFxHFjh
	 rc4ipaMcTjBq6gtqf0kqi/y8IS7xD1xXSWbJBCRM=
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/107046] [13 Regression] Recent FP range work
 causing inf-2 to be miscompiled on rx-elf
Date: Tue, 27 Sep 2022 08:59:34 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 13.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth 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: 13.0
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-107046-4-acpu8AmU8k@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-107046-4@http.gcc.gnu.org/bugzilla/>
References: <bug-107046-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=3D107046

--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
Ah, probably the

void test(double f, double i)
{
...
  if (i !=3D __builtin_inf())
    abort ();

int main()
{
  test (34.0, __builtin_inf());
...

test is "miscompiled", similar to what we see in povray.

We can probably gate parts of the testcase with

#if __FINITE_MATH_ONLY__ =3D=3D 0=