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 target/99807] [11 Regression] ICE in vect_slp_analyze_node_operations_1, at tree-vect-slp.c:3727
Date: Mon, 29 Mar 2021 11:13:21 +0000 [thread overview]
Message-ID: <bug-99807-4-7NG9Vssf2h@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99807-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99807
--- Comment #5 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:8cf2812cfceaf464dff99651b2d911d6e12b52b7
commit r11-7889-g8cf2812cfceaf464dff99651b2d911d6e12b52b7
Author: Richard Biener <rguenther@suse.de>
Date: Mon Mar 29 13:10:37 2021 +0200
tree-optimization/99807 - avoid bogus assert with permute SLP node
This avoids asserting anything on the SLP_TREE_REPRESENTATIVE of
an SLP permute node (which shouldn't be there).
2021-03-29 Richard Biener <rguenther@suse.de>
PR tree-optimization/99807
* tree-vect-slp.c (vect_slp_analyze_node_operations_1): Move
assert below VEC_PERM handling.
* gfortran.dg/vect/pr99807.f90: New testcase.
next prev parent reply other threads:[~2021-03-29 11:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-29 5:09 [Bug target/99807] New: " asolokha at gmx dot com
2021-03-29 7:34 ` [Bug target/99807] " ktkachov at gcc dot gnu.org
2021-03-29 7:55 ` [Bug target/99807] [11 Regression] " rguenth at gcc dot gnu.org
2021-03-29 8:15 ` rguenth at gcc dot gnu.org
2021-03-29 8:35 ` rguenth at gcc dot gnu.org
2021-03-29 11:13 ` cvs-commit at gcc dot gnu.org [this message]
2021-03-29 11:13 ` 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-99807-4-7NG9Vssf2h@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).