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/107212] [11 Regression] Wrong vectorizer code since r11-718-gc735929a2503a7d0
Date: Tue, 24 Jan 2023 15:22:41 +0000 [thread overview]
Message-ID: <bug-107212-4-cZEBsvI84F@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107212-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107212
--- Comment #9 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:2461fa40fc24a403dc8149338f44b0e4aef4f173
commit r11-10480-g2461fa40fc24a403dc8149338f44b0e4aef4f173
Author: Richard Biener <rguenther@suse.de>
Date: Tue Oct 11 11:34:55 2022 +0200
tree-optimization/107212 - SLP reduction of reduction paths
The following fixes an issue with how we handle epilogue generation
for SLP reductions of reduction paths where the actual live lanes
are not "canonical". We need to make sure to identify all live
lanes as reductions and thus have to iterate over all participating
SLP lanes when walking the reduction SSA use-def chain. Also the
previous attempt likely to mitigate such issue in
vectorizable_live_operation is misguided and has to be removed.
PR tree-optimization/107212
* tree-vect-loop.c (vectorizable_reduction): Make sure to
set STMT_VINFO_REDUC_DEF for all live lanes in a SLP
reduction.
(vectorizable_live_operation): Do not pun to the SLP
node representative for reduction epilogue generation.
* gcc.dg/vect/pr107212-1.c: New testcase.
* gcc.dg/vect/pr107212-2.c: Likewise.
(cherry picked from commit ee467644c53ee2f7d633a8e1f53603feafab4351)
next prev parent reply other threads:[~2023-01-24 15:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-11 8:06 [Bug c/107212] New: -O2 and -O3 optimizer bug aosman9xx9 at gmail dot com
2022-10-11 8:32 ` [Bug tree-optimization/107212] [11/12/13 Regression] Wrong vectorizer code since r11-718-gc735929a2503a7d0 marxin at gcc dot gnu.org
2022-10-11 8:42 ` rguenth at gcc dot gnu.org
2022-10-11 8:43 ` rguenth at gcc dot gnu.org
2022-10-11 8:44 ` marxin at gcc dot gnu.org
2022-10-11 9:30 ` rguenth at gcc dot gnu.org
2022-10-11 9:30 ` rguenth at gcc dot gnu.org
2022-10-11 11:15 ` cvs-commit at gcc dot gnu.org
2022-10-11 11:16 ` [Bug tree-optimization/107212] [11/12 " rguenth at gcc dot gnu.org
2022-10-17 13:10 ` cvs-commit at gcc dot gnu.org
2023-01-24 15:22 ` cvs-commit at gcc dot gnu.org [this message]
2023-01-24 15:23 ` [Bug tree-optimization/107212] [11 " 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-107212-4-cZEBsvI84F@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).