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/103029] [12 regression] gcc.dg/vect/pr82436.c ICEs on r12-4818
Date: Tue, 02 Nov 2021 17:49:53 +0000 [thread overview]
Message-ID: <bug-103029-4-jQK99YJB2B@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103029-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103029
--- Comment #6 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:164bbf701ff10ff44e272525e8f462ed3ff1cf43
commit r12-4850-g164bbf701ff10ff44e272525e8f462ed3ff1cf43
Author: Richard Biener <rguenther@suse.de>
Date: Tue Nov 2 18:47:14 2021 +0100
tree-optimization/103029 - ensure vect loop versioning constraint on PHIs
PHI nodes in vectorizer loop versioning need to maintain the same
order of PHI arguments to not disturb SLP discovery. The following
adds an assertion and mitigation in case loop versioning breaks this
which happens more often after the recent reorg.
2021-11-02 Richard Biener <rguenther@suse.de>
PR tree-optimization/103029
* tree-vect-loop-manip.c (vect_loop_versioning): Ensure
the PHI nodes in the loop maintain their original operand
order.
next prev parent reply other threads:[~2021-11-02 17:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-01 18:43 [Bug tree-optimization/103029] New: " seurer at gcc dot gnu.org
2021-11-01 18:46 ` [Bug tree-optimization/103029] " seurer at gcc dot gnu.org
2021-11-02 3:46 ` luoxhu at gcc dot gnu.org
2021-11-02 6:04 ` luoxhu at gcc dot gnu.org
2021-11-02 7:45 ` rguenth at gcc dot gnu.org
2021-11-02 15:56 ` rguenth at gcc dot gnu.org
2021-11-02 17:49 ` cvs-commit at gcc dot gnu.org [this message]
2021-11-02 17:50 ` rguenth at gcc dot gnu.org
2021-11-03 1:22 ` luoxhu 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-103029-4-jQK99YJB2B@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).