public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/97513] [11 regression] aarch64 SVE regressions since r11-3822
Date: Wed, 17 Mar 2021 13:13:02 +0000 [thread overview]
Message-ID: <bug-97513-4-Dkd9Qwe8fK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97513-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97513
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
I chose to bisect randomly one test, gcc.target/aarch64/sve/slp_perm_1.c
started FAILing with r11-3823 and FAILs even with current trunk, the difference
seems to be that previously it was using the SVE variable length vectors and
now it uses fixed V16QImode vectors.
As this PR mentions a lot of different FAILs, some started earlier, others
later, some got fixed afterwards, others not, it is hard to find out what
can/should be done.
I can't reproduce the gcc.target/aarch64/sve/mask_load_slp_1.c FAILs, I get 48
/ 40 instructions as expected even with r11-3822.
I get 40 / 32 in r11-3823 up to r11-4480, and starting from r11-4481 again 48 /
40 until now.
next prev parent reply other threads:[~2021-03-17 13:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-21 9:38 [Bug tree-optimization/97513] New: " clyon at gcc dot gnu.org
2020-10-21 10:32 ` [Bug target/97513] " rguenth at gcc dot gnu.org
2020-10-21 13:14 ` acoplan at gcc dot gnu.org
2020-10-21 13:17 ` clyon at gcc dot gnu.org
2020-11-19 18:02 ` rsandifo at gcc dot gnu.org
2020-11-19 19:56 ` clyon at gcc dot gnu.org
2021-01-14 9:30 ` rguenth at gcc dot gnu.org
2021-03-09 14:26 ` rguenth at gcc dot gnu.org
2021-03-17 13:13 ` jakub at gcc dot gnu.org [this message]
2021-04-01 16:11 ` rsandifo at gcc dot gnu.org
2021-04-07 14:22 ` cvs-commit at gcc dot gnu.org
2021-04-08 10:21 ` jakub at gcc dot gnu.org
2021-04-09 11:45 ` rsandifo 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-97513-4-Dkd9Qwe8fK@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).