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/96698] [10 Regression] ICE during GIMPLE pass:vect
Date: Wed, 02 Dec 2020 11:41:06 +0000 [thread overview]
Message-ID: <bug-96698-4-nAE4onFeyA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96698-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96698
--- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-10 branch has been updated by Richard Biener
<rguenth@gcc.gnu.org>:
https://gcc.gnu.org/g:66dd83c8840a9a28f6209922b8abd5783a255207
commit r10-9106-g66dd83c8840a9a28f6209922b8abd5783a255207
Author: Richard Biener <rguenther@suse.de>
Date: Wed Aug 26 15:12:17 2020 +0200
tree-optimization/96698 - fix ICE when vectorizing nested cycles
This fixes vectorized PHI latch edge updating and delay it until
all of the loop is code generated to deal with the case that the
latch def is a PHI in the same block.
2020-08-26 Richard Biener <rguenther@suse.de>
PR tree-optimization/96698
* tree-vectorizer.h (loop_vec_info::reduc_latch_defs): New.
(loop_vec_info::reduc_latch_slp_defs): Likewise.
* tree-vect-stmts.c (vect_transform_stmt): Only record
stmts to update PHI latches from, perform the update ...
* tree-vect-loop.c (vect_transform_loop): ... here after
vectorizing those PHIs.
(info_for_reduction): Properly handle non-reduction PHIs.
* gcc.dg/vect/pr96698.c: New testcase.
(cherry picked from commit 2130efe6ac7beba72d289e3dd145daa10aeaed54)
next prev parent reply other threads:[~2020-12-02 11:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-19 1:43 [Bug tree-optimization/96698] New: aarch64: " yangyang305 at huawei dot com
2020-08-19 10:16 ` [Bug tree-optimization/96698] " marxin at gcc dot gnu.org
2020-08-24 9:07 ` [Bug tree-optimization/96698] [10/11 Regression] " rguenth at gcc dot gnu.org
2020-08-26 14:02 ` cvs-commit at gcc dot gnu.org
2020-09-04 13:43 ` [Bug tree-optimization/96698] [10 " cvs-commit at gcc dot gnu.org
2020-12-02 11:41 ` cvs-commit at gcc dot gnu.org [this message]
2020-12-02 11:41 ` cvs-commit at gcc dot gnu.org
2020-12-02 11:41 ` 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-96698-4-nAE4onFeyA@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).