public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/101895] [11 Regression] SLP Vectorizer change pushes VEC_PERM_EXPR into bad location spoiling further optimization opportunities
Date: Wed, 16 Mar 2022 07:10:20 +0000 [thread overview]
Message-ID: <bug-101895-4-jDe62MhuN4@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101895-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101895
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|12.0 |11.3
Summary|[11/12 Regression] SLP |[11 Regression] SLP
|Vectorizer change pushes |Vectorizer change pushes
|VEC_PERM_EXPR into bad |VEC_PERM_EXPR into bad
|location spoiling further |location spoiling further
|optimization opportunities |optimization opportunities
Known to work| |12.0
Resolution|FIXED |---
Status|RESOLVED |NEW
--- Comment #8 from Richard Biener <rguenth at gcc dot gnu.org> ---
Fixed on trunk, keeping for reference purposes (backporting is not intended).
There's also still the possibility to improve how the vectorizer handles this
instead of fixing up after the fact (but that's for the future).
next prev parent reply other threads:[~2022-03-16 7:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-13 5:01 [Bug tree-optimization/101895] New: [11/12 " law at gcc dot gnu.org
2021-08-13 5:24 ` [Bug tree-optimization/101895] " pinskia at gcc dot gnu.org
2021-08-13 5:24 ` pinskia at gcc dot gnu.org
2021-08-16 7:49 ` rguenth at gcc dot gnu.org
2021-08-25 4:40 ` law at gcc dot gnu.org
2021-08-25 7:19 ` rguenth at gcc dot gnu.org
2022-03-11 23:51 ` roger at nextmovesoftware dot com
2022-03-15 9:06 ` cvs-commit at gcc dot gnu.org
2022-03-15 23:44 ` roger at nextmovesoftware dot com
2022-03-16 7:10 ` rguenth at gcc dot gnu.org [this message]
2022-03-16 23:13 ` [Bug tree-optimization/101895] [11 " law at gcc dot gnu.org
2022-03-17 23:18 ` law at gcc dot gnu.org
2022-04-21 7:50 ` rguenth at gcc dot gnu.org
2023-05-29 10:05 ` jakub 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-101895-4-jDe62MhuN4@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).