From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 9F691385828E; Tue, 2 Jan 2024 11:35:35 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 9F691385828E DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1704195335; bh=BaKC3T2DWBnyb90RbYn9+GCTPoFWFRNC/r/l+8P80S4=; h=From:To:Subject:Date:In-Reply-To:References:From; b=Z7syNLAJC0gKGtmsiESxsPdHzjWXkoGsLPmiHshEIbNk2EQCSZCKKsUcusUr6X1lZ +E1BELMN6WPZSJGzpll4rwHgEaY0lL436A8qEIkJr9P9ckzE7G28yEnhisdM//tgQP 7Khkta/ZboULa5K+U0oESsEbOWNIl2ZinNWm4Snw= From: "tnfchris at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/113163] [14 Regression][GCN] ICE in vect_peel_nonlinear_iv_init, at tree-vect-loop.cc:9420 Date: Tue, 02 Jan 2024 11:35:34 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: middle-end X-Bugzilla-Version: 14.0 X-Bugzilla-Keywords: ice-on-valid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: tnfchris at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: tnfchris at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- 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=3D113163 --- Comment #12 from Tamar Christina --- (In reply to Andrew Stubbs from comment #11) > (In reply to Tamar Christina from comment #7) > > This seems to happen because the vectorizer decides to use partial vect= ors > > to vectorize the loop and the target picks a nonlinear induction step w= hich > > we can't support for early breaks. >=20 > In which hook is this selected? >=20 > I'm not aware of this being a deliberate choice we made... I haven't looked into why on the target we get a nonlinear induction (mostly because I don't know much about the target). I however wasn't able to repro= duce it on SVE and x86_64 even when forcing partial vectors. So I guess it's more accurate to say "something about the target" is making= the vectorizer pick a nonlinear induction. most likely missing support for something. Note that the testcase does work if partial vectors is turned off. So It sh= ould work fine if the vectorizer retries without partial vectors. waiting for Richi to come back from holiday to review the patch and should = be fixed.=