From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 94B683858C53; Tue, 31 Oct 2023 09:12:23 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 94B683858C53 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1698743543; bh=WSEha7dQtXD5bNMTMqywDwuHnTHrqvc1wppnOxvlAd0=; h=From:To:Subject:Date:In-Reply-To:References:From; b=UViTO4V6k3NnsCDMi25xCM3WQQ7oTo/n5TxLCGSTJRBuAGxH5RbaHQ9wCISPCRwWm 1A4UXK+tf4lT1vlpIHkBX88rOBCWHZnd181GHbdXsidLj8QjKsvJ/W3N/ZMlBsYlkh O4L8wO6AqAJA+wxp+ov2VBZmGxQLiIfVrB9A7Oec= From: "avieira at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/112282] [14 Regression] wrong code (generated code hangs) at -O3 on x86_64-linux-gnu since r14-4777-g88c27070c25309 Date: Tue, 31 Oct 2023 09:12:20 +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: 14.0 X-Bugzilla-Keywords: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: avieira at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 14.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=3D112282 --- Comment #10 from avieira at gcc dot gnu.org --- So I had a look at that u_lsm.72_510 variable and it's only undefined if we don't loop, but if we don't loop then u_lsm_flag is set to 0 and we don't u= se u_lsm. So it's OK. I also checked and the early exits are covered by the sa= me mechanism. So really the question is, why does irange think the range is [-21, 0]. Any= one have an idea of how to debug this?=