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/101158] [10/11 Regression] ICE in gimple_call_arg, at gimple.h:3247
Date: Fri, 25 Jun 2021 09:06:10 +0000 [thread overview]
Message-ID: <bug-101158-4-VeHRgJDsHv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101158-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101158
--- Comment #4 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:48097089ae539bd5c2649681f93ce4a6bad72b11
commit r11-8655-g48097089ae539bd5c2649681f93ce4a6bad72b11
Author: Richard Biener <rguenther@suse.de>
Date: Tue Jun 22 09:24:24 2021 +0200
tree-optimization/101158 - adjust SLP call matching sequence
This moves the check for same operands after verifying we're
facing compatible calls.
2021-06-22 Richard Biener <rguenther@suse.de>
PR tree-optimization/101158
* tree-vect-slp.c (vect_build_slp_tree_1): Move same operand
checking after checking for matching operation.
* gfortran.dg/pr101158.f90: New testcase.
(cherry picked from commit 7a22d8a764418265680a6bb9a9aec31e984eb015)
next prev parent reply other threads:[~2021-06-25 9:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-22 4:06 [Bug tree-optimization/101158] New: " asolokha at gmx dot com
2021-06-22 6:54 ` [Bug tree-optimization/101158] " rguenth at gcc dot gnu.org
2021-06-22 9:01 ` cvs-commit at gcc dot gnu.org
2021-06-22 9:04 ` [Bug tree-optimization/101158] [10/11 Regression] " rguenth at gcc dot gnu.org
2021-06-25 9:06 ` cvs-commit at gcc dot gnu.org [this message]
2022-02-17 10:48 ` [Bug tree-optimization/101158] [10 " cvs-commit at gcc dot gnu.org
2022-02-17 10:51 ` 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-101158-4-VeHRgJDsHv@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).