public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/101445] [11/12 Regression] wrong code at -O3 on x86_64-linux-gnu
Date: Wed, 14 Jul 2021 11:09:15 +0000 [thread overview]
Message-ID: <bug-101445-4-qMlUU8A4qI@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101445-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101445
--- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-11 branch has been updated by Richard Biener
<rguenth@gcc.gnu.org>:
https://gcc.gnu.org/g:1eee5fa556432fb6eab3a479c95609c5f3791ccb
commit r11-8736-g1eee5fa556432fb6eab3a479c95609c5f3791ccb
Author: Richard Biener <rguenther@suse.de>
Date: Wed Jul 14 11:06:58 2021 +0200
tree-optimization/101445 - fix negative stride SLP vect with gaps
The following fixes the IV adjustment for the gap in a negative
stride SLP vectorization. The adjustment was in the wrong direction,
now fixes as in the patch.
2021-07-14 Richard Biener <rguenther@suse.de>
PR tree-optimization/101445
* tree-vect-stmts.c (vectorizable_load): Do the gap adjustment
of the IV in the correct direction for negative stride
accesses.
* gcc.dg/vect/pr101445.c: New testcase.
(cherry picked from commit a967a3efd39280fe3f5774e45490e991f8e99059)
next prev parent reply other threads:[~2021-07-14 11:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-14 2:50 [Bug tree-optimization/101445] New: " qrzhang at gatech dot edu
2021-07-14 2:50 ` [Bug tree-optimization/101445] " qrzhang at gatech dot edu
2021-07-14 2:58 ` [Bug tree-optimization/101445] [11/12 Regression] " pinskia at gcc dot gnu.org
2021-07-14 6:12 ` rguenth at gcc dot gnu.org
2021-07-14 8:58 ` rguenth at gcc dot gnu.org
2021-07-14 10:31 ` cvs-commit at gcc dot gnu.org
2021-07-14 11:09 ` cvs-commit at gcc dot gnu.org [this message]
2021-07-14 11:09 ` rguenth 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-101445-4-qMlUU8A4qI@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).