From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id F3E2F38582AB; Thu, 19 Jan 2023 01:15:18 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org F3E2F38582AB DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1674090919; bh=LMHJGEZqkm0abzCzT3eJiaeybMAsq7q/3K0RkPwJgKg=; h=From:To:Subject:Date:In-Reply-To:References:From; b=nWXX8A36dWLvWmgoh0BmIjrFe9ab7sJGS5tNCQ/SjW8d28+rob5yyVaN0XW+npQbA RQaCizIcmSc1q7lZncAtp5RKxE9JpnAWB7Dz/IjtPkD2KiBWV+IH/i87ZAeMc3jzld O9xG1y1eUA2EVRW0y16iP+akvblcQyKll+CsTHZ0= From: "xry111 at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/107608] [13 Regression] Failure on fold-overflow-1.c and pr95115.c Date: Thu, 19 Jan 2023 01:15:17 +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: missed-optimization, wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: xry111 at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P1 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: 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=3D107608 --- Comment #42 from Xi Ruoyao --- (In reply to Richard Biener from comment #41) > We could fix the testcase with >=20 > diff --git a/gcc/testsuite/gcc.dg/pr95115.c b/gcc/testsuite/gcc.dg/pr9511= 5.c > index 69c4f83250c..09273e445d2 100644 > --- a/gcc/testsuite/gcc.dg/pr95115.c > +++ b/gcc/testsuite/gcc.dg/pr95115.c > @@ -17,6 +17,7 @@ int > main (void) > { > double r =3D x (); > + volatile double rr =3D r; > if (!__builtin_isnan (r)) > abort (); > if (!fetestexcept (FE_INVALID)) >=20 > that preserves optimizing the isnan check but also preserves the computat= ion > and checks the non-propagation of a NaN. Hmm, so it means we cannot rely on Inf / Inf to raise an exception? Then we need to fix Glibc...=