public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "seurer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/97494] New: [11 regression] several vector test case failures starting with r11-3966
Date: Mon, 19 Oct 2020 15:07:22 +0000 [thread overview]
Message-ID: <bug-97494-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97494
Bug ID: 97494
Summary: [11 regression] several vector test case failures
starting with r11-3966
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: seurer at gcc dot gnu.org
Target Milestone: ---
g:429ad0bb0d3dc77e44f95620341da4938d49168e, r11-3966: 109 failures
On all powerpc64 both BE and LE:
FAIL: gcc.dg/vect/slp-11b.c -flto -ffat-lto-objects scan-tree-dump-times vect
"vectorizing stmts using SLP" 0
FAIL: gcc.dg/vect/slp-11b.c scan-tree-dump-times vect "vectorizing stmts using
SLP" 0
FAIL: gcc.dg/vect/slp-21.c -flto -ffat-lto-objects scan-tree-dump-times vect
"vectorizing stmts using SLP" 2
FAIL: gcc.dg/vect/slp-21.c scan-tree-dump-times vect "vectorizing stmts using
SLP" 2
Some extras on power7 BE:
FAIL: gcc.dg/vect/pr97428.c -flto -ffat-lto-objects scan-tree-dump-times vect
"vectorizing stmts using SLP" 2
FAIL: gcc.dg/vect/pr97428.c scan-tree-dump-times vect "vectorizing stmts using
SLP" 2
FAIL: gcc.dg/vect/vect-complex-5.c -flto -ffat-lto-objects
scan-tree-dump-times vect "vectorizing stmts using SLP" 2
FAIL: gcc.dg/vect/vect-complex-5.c scan-tree-dump-times vect "vectorizing stmts
using SLP" 2
commit 429ad0bb0d3dc77e44f95620341da4938d49168e (HEAD)
Author: Richard Biener <rguenther@suse.de>
Date: Thu Oct 15 11:55:53 2020 +0200
tree-optimization/97428 - split SLP groups for loop vectorization
This enables SLP store group splitting also for loop vectorization.
For the existing testcase gcc.dg/vect/vect-complex-5.c this then
generates much better code, likewise for the PR97428 testcase.
Both of those have a splitting opportunity splitting the group
into two equal (vector-sized) halves, still the patch enables
quite arbitrary splitting since generally the interleaving scheme
results in quite awkward code for even small groups. If any
problems surface with this it's easy to restrict the splitting
to known-good cases.
2020-10-15 Richard Biener <rguenther@suse.de>
PR tree-optimization/97428
* tree-vect-slp.c (vect_analyze_slp_instance): Split store
groups also for loop vectorization.
* gcc.dg/vect/vect-complex-5.c: Expect to SLP.
* gcc.dg/vect/pr97428.c: Likewise.
next reply other threads:[~2020-10-19 15:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-19 15:07 seurer at gcc dot gnu.org [this message]
2020-10-19 15:21 ` [Bug tree-optimization/97494] " rguenth at gcc dot gnu.org
2020-10-21 9:18 ` clyon at gcc dot gnu.org
2020-12-11 12:15 ` ro at gcc dot gnu.org
2021-01-14 9:27 ` rguenth at gcc dot gnu.org
2021-01-18 14:00 ` rguenth at gcc dot gnu.org
2021-01-18 14:19 ` rguenth at gcc dot gnu.org
2021-01-18 14:20 ` cvs-commit at gcc dot gnu.org
2021-03-11 12:32 ` cvs-commit at gcc dot gnu.org
2021-03-11 13:03 ` rguenth at gcc dot gnu.org
2021-03-11 13:05 ` cvs-commit at gcc dot gnu.org
2021-03-11 13:13 ` cvs-commit at gcc dot gnu.org
2021-03-11 13:16 ` rguenth at gcc dot gnu.org
2021-03-11 18:48 ` seurer at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-97494-4@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).