From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 140FB394743E; Mon, 5 Dec 2022 16:40:28 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 140FB394743E DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1670258429; bh=Pnn7FAbHNpCOaOaJPx9vWJLvEsQBN+4WEgbH7cxzBZI=; h=From:To:Subject:Date:In-Reply-To:References:From; b=dnFH/ilME/ktncjDOmRgd3XK+EnnTvHs3wFSRrIoY0BJtmzcfBWRAjWj92HhhVq4o M5i1kTdP/Ss8vaTzTMDy74d8WZ6A4TzD1egreDRH+U4i7ZZBAkXsJqDVyAkzy5tiS5 wxyW7h68fIhgxioWp5Io3Vjnq1SA55v5KP+eCqDI= From: "jakub at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/107967] [13 regression] The gcc commit r13-3923 caused the glibc make check fails. Date: Mon, 05 Dec 2022 16:40:28 +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: needs-reduction, wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: jakub at gcc dot gnu.org X-Bugzilla-Status: NEW 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: 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=3D107967 --- Comment #5 from Jakub Jelinek --- (In reply to caiyinyu from comment #2) > I tested with latest gcc(commit 102f3cef568), and these fails still exist. Do the glibc test logs provide some details on what exactly failed, if it i= s a wrong-code issue or if the testcase expects some floating point exception t= hat isn't triggered?=