From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 403E63894C07; Mon, 5 Dec 2022 10:35:44 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 403E63894C07 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1670236544; bh=07xejITUyJDHayubKgz10DQGyK0jozmYJg9b6oMNySY=; h=From:To:Subject:Date:In-Reply-To:References:From; b=oiyaQaNgzEY1fO5yBZ2m3cuk/+Zg4ceYgNtDEjsVHJ14Edcoj7FBEvhrnWY13TJ2F cbAX9a2a1vzW0a13WacKRibiJ12qOScASvIhahwDq23TF8QeP/ELXLfVZDYImR89e2 Fc9uDoCYmMKK7a/MG8oPU7I9GXeuTJUi8sfGseRY= 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 10:35:43 +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: 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: cc short_desc 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 Jakub Jelinek changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aldyh at gcc dot gnu.org Summary|[13 regression] The gcc |[13 regression] The gcc |commit 2f7f9edd28d caused |commit r13-3923 caused the |the glibc make check fails. |glibc make check fails. --- Comment #3 from Jakub Jelinek --- r13-3923-g2f7f9edd28d75a85a33599978f23811e679e443d Note, I've just committed the PR107879 fix, but that one is for the reverse operations. And, we have still unresolved the PR107608 which on the other side could ve= ry well be related or the cause of this. BTW, Aldy, is there a way to disable all range related optimizations through some command line option? In the past, -fno-tree-vrp would do the trick, b= ut now that the ranger is used in lots of passes, I don't know what else to us= e.=