From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 55EBF388F066; Mon, 29 Jun 2020 12:12:48 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 55EBF388F066 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1593432768; bh=SA70CLjawD29Kjxd66ek13yykoo8iZcGFvspkjneRdw=; h=From:To:Subject:Date:In-Reply-To:References:From; b=m5XOUKKzU/4Vdba+BrbF0WFtKboQ4G/A3KV8lXCSAffMy5+3YAamVfQ2fxLXBCDYc QzgfUzzc0rciODHe3jGfVyCaN0X9BDhV1ZKBLnqEKh+n7msa34d4D4lIcqI3+qwRBq Ptc83rOgIlovKoXnkaHqBZCNifu+JPIUVpXXSfPs= From: "rguenth at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/95960] GCC should re-vectorize vector code with larger VF Date: Mon, 29 Jun 2020 12:12:48 +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: 11.0 X-Bugzilla-Keywords: 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: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: attachments.created 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 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Jun 2020 12:12:48 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D95960 --- Comment #1 from Richard Biener --- Created attachment 48801 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=3D48801&action=3Dedit start So quick experiments show where we need to do adjustments. We do have an explicit SLP_TREE_LANES we could use for "true" scalar lanes as compared to the number of "scalar" stmts but uses might have been transitioned not exactly along this boundary. Then there's of course 'group_size' which can mean either depending on context. The biggest churn is likely in dataref group analysis where we IMHO also want a "lanes" representation.=