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/94443] [10 Regression] 510.parest_r and 526.blender_r ICE: verify_ssa failed since r10-7491-gbd0f22a8d5caea8905f38ff1fafce31c1b7d33ad
Date: Fri, 03 Apr 2020 08:09:09 +0000 [thread overview]
Message-ID: <bug-94443-4-BawvVxGt23@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94443-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94443
--- Comment #14 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Kewen Lin <linkw@gcc.gnu.org>:
https://gcc.gnu.org/g:4441ecedc3d74114683761901075085651928c52
commit r10-7531-g4441ecedc3d74114683761901075085651928c52
Author: Kewen Lin <linkw@linux.ibm.com>
Date: Fri Apr 3 02:10:08 2020 -0500
Fix PR94443 with gsi_insert_seq_before [PR94443]
This patch is to fix the stupid mistake by using
gsi_insert_seq_before instead of gsi_insert_before.
BTW, the regression testing on one x86_64 machine from CFarm is
unable to reveal it (I guess due to native arch sandybridge?), so I
specified additional option -march=znver2 and verified the coverage.
Bootstrapped/regtested on powerpc64le-linux-gnu (P9) and
x86_64-pc-linux-gnu, also verified the fail cases in related PRs.
2020-04-03 Kewen Lin <linkw@gcc.gnu.org>
gcc/
PR tree-optimization/94443
* tree-vect-loop.c (vectorizable_live_operation): Use
gsi_insert_seq_before to replace gsi_insert_before.
gcc/testsuite/
PR tree-optimization/94443
* gcc.dg/vect/pr94443.c: New test.
next prev parent reply other threads:[~2020-04-03 8:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-01 14:27 [Bug tree-optimization/94443] New: " marxin at gcc dot gnu.org
2020-04-01 14:27 ` [Bug tree-optimization/94443] " marxin at gcc dot gnu.org
2020-04-01 14:39 ` marxin at gcc dot gnu.org
2020-04-01 14:41 ` marxin at gcc dot gnu.org
2020-04-01 15:22 ` linkw at gcc dot gnu.org
2020-04-02 0:42 ` linkw at gcc dot gnu.org
2020-04-02 2:38 ` linkw at gcc dot gnu.org
2020-04-02 7:39 ` rguenther at suse dot de
2020-04-02 7:42 ` linkw at gcc dot gnu.org
2020-04-02 7:48 ` linkw at gcc dot gnu.org
2020-04-02 9:25 ` marxin at gcc dot gnu.org
2020-04-02 13:23 ` linkw at gcc dot gnu.org
2020-04-02 13:42 ` raj.khem at gmail dot com
2020-04-02 13:44 ` raj.khem at gmail dot com
2020-04-02 14:31 ` linkw at gcc dot gnu.org
2020-04-03 8:09 ` cvs-commit at gcc dot gnu.org [this message]
2020-04-03 11:36 ` linkw at gcc dot gnu.org
2020-04-03 11:45 ` marxin at gcc dot gnu.org
2020-04-03 11:50 ` linkw at gcc dot gnu.org
2020-04-03 16:10 ` florin.iucha at amd dot com
2020-04-09 14:30 ` dpochepk at gmail dot com
2020-04-17 8:55 ` cvs-commit 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-94443-4-BawvVxGt23@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).