From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 135173858C5F; Tue, 31 Jan 2023 07:25:28 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 135173858C5F DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1675149928; bh=zQ73v0Qhu7JkRr0jzHj9efoID99NldigoFzMYG9aNaI=; h=From:To:Subject:Date:In-Reply-To:References:From; b=WTRLCr17J1qBPEgVsEKd0EJOq13vBwo8xq/0yvbd8atQQgDzCCawqEd9v/x8ig6rL L78a5FF79lpG2wohPhYuZJNDzoqzRvpcbdFOUk2/F1shMMWhT8QErN25JgR1cmX7LL is0BgXq1AOc/r1s6DaZNUzOAcM+YarjcIavE+Qp8= From: "rguenth at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/108601] [13 Regression] vector peeling ICEs with PGO + LTO + IPA inlining in gcc_r in SPEC2017 Date: Tue, 31 Jan 2023 07:25:27 +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: ice-on-valid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: rguenth 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 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=3D108601 Richard Biener changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |liuhongt at gcc dot gnu.or= g, | |rguenth at gcc dot gnu.org --- Comment #2 from Richard Biener --- To me it's obvious that the path in the backtrace gets a non-constant niter bump since we're dealing with epilog peeling. Either we need to reject this when requiring a peeled epilogue or we should deal with a non-constant skip_nite= rs. This was introduced with r13-2503-gc13223b790bbc5. Btw, I wonder why we need to use this function instead of re-using the IV from the vectorized loop (or extracting the "last" value from the vectorized variant). It should be possible to construct a testcase with a vectorizable non-linea= r IV that requires peeling of the epilog?=