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/97500] [11 Regression] ICE in vect_schedule_slp_instance, at tree-vect-slp.c:5094 since r11-3823-g126ed72b9f48f853
Date: Wed, 21 Oct 2020 09:43:16 +0000 [thread overview]
Message-ID: <bug-97500-4-w6fTVY6BQx@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97500-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97500
--- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Richard Biener <rguenth@gcc.gnu.org>:
https://gcc.gnu.org/g:d94093013877cde3dce5c243099ad54668849400
commit r11-4185-gd94093013877cde3dce5c243099ad54668849400
Author: Richard Biener <rguenther@suse.de>
Date: Wed Oct 21 10:54:54 2020 +0200
tree-optimization/97500 - avoid SLP backedges for inductions
Inductions are not vectorized as cycle but materialized from SCEV data.
Filling in backedge SLP nodes confuses this process.
2020-10-21 Richard Biener <rguenther@suse.de>
PR tree-optimization/97500
* tree-vect-slp.c (vect_analyze_slp_backedges): Do not
fill backedges for inductions.
* gfortran.dg/pr97500.f90: New testcase.
next prev parent reply other threads:[~2020-10-21 9:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-20 7:34 [Bug tree-optimization/97500] New: " marxin at gcc dot gnu.org
2020-10-20 7:34 ` [Bug tree-optimization/97500] " marxin at gcc dot gnu.org
2020-10-20 9:46 ` rguenth at gcc dot gnu.org
2020-10-21 9:43 ` cvs-commit at gcc dot gnu.org [this message]
2020-10-21 9:43 ` 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-97500-4-w6fTVY6BQx@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).