From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 880C93858434; Thu, 19 Jan 2023 13:22:05 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 880C93858434 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1674134525; bh=Ymt94tLr++/MDOSCWDwekjJ62zVCU80NK2kWc6R9ArI=; h=From:To:Subject:Date:In-Reply-To:References:From; b=RxO5Xnd6j9bz5g0kDjRJDdMDz1vY8KS5AAnDne9b3A9j0LedmreJLPJjRA6OrQKQp o8OrLj2n8LG4hdrlamTzaSRZKgX5egxaXSkyw9ev9yQ3HHBpF0S/7rPK9NFA2De1ns /WEiVMlwz0X+E1C6mVBahklPD/SIB+JfrPKcC0hk= From: "rguenth at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/100061] [10/11 Regression] Comparison guarding undefined behaviour disappears Date: Thu, 19 Jan 2023 13:22:04 +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: 10.3.0 X-Bugzilla-Keywords: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: rguenth at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 10.5 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: short_desc cf_known_to_fail cf_known_to_work 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=3D100061 Richard Biener changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|[10/11/12/13 Regression] |[10/11 Regression] |Comparison guarding |Comparison guarding |undefined behaviour |undefined behaviour |disappears |disappears Known to fail| |11.3.1 Known to work| |12.1.0, 13.0 --- Comment #14 from Richard Biener --- Btw, eventually the refactoring done for PR105142 in r12-8012-gfc8d9e449703= 2d will help, at least the fixed problem is of similar nature. The original testcase seems fixed by this at least as we are no longer expanding the guarded c + 1.=