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/97496] [11 Regression] during during GIMPLE pass: cddce since r11-4005-g6c6e0cafa38cee83 Date: Tue, 20 Oct 2020 07:03:10 +0000 [thread overview] Message-ID: <bug-97496-4-PESZjl3bH0@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97496-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97496 --- Comment #4 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:a335f6f4ee5cb4f7dbfef52e17bf854ae42c1216 commit r11-4084-ga335f6f4ee5cb4f7dbfef52e17bf854ae42c1216 Author: Richard Biener <rguenther@suse.de> Date: Tue Oct 20 08:14:54 2020 +0200 tree-optimization/97496 - avoid SLP externs in patterns I forgot to guard the promotion to external for the case where the def is in a pattern. 2020-10-20 Richard Biener <rguenther@suse.de> PR tree-optimization/97496 * tree-vect-slp.c (vect_get_and_check_slp_defs): Guard extern promotion with not in pattern. * gcc.dg/vect/bb-slp-pr97496.c: New testcase.
next prev parent reply other threads:[~2020-10-20 7:03 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-19 16:09 [Bug c/97496] New: ice during during GIMPLE pass: cddce dcb314 at hotmail dot com 2020-10-19 16:15 ` [Bug tree-optimization/97496] [11 Regression] during during GIMPLE pass: cddce since r11-4005-g6c6e0cafa38cee83 marxin at gcc dot gnu.org 2020-10-19 16:15 ` marxin at gcc dot gnu.org 2020-10-20 6:00 ` rguenth at gcc dot gnu.org 2020-10-20 7:03 ` cvs-commit at gcc dot gnu.org [this message] 2020-10-20 7:03 ` 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-97496-4-PESZjl3bH0@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: linkBe 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).