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/101242] Segfault in SLP vectorizor after g:2ad71efb5de
Date: Tue, 29 Jun 2021 08:35:20 +0000	[thread overview]
Message-ID: <bug-101242-4-8q9FLqu9jV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101242-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101242

--- Comment #7 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:c01760bc548ba79bc9ac15168b27fe7aabcb19ae

commit r12-1866-gc01760bc548ba79bc9ac15168b27fe7aabcb19ae
Author: Richard Biener <rguenther@suse.de>
Date:   Tue Jun 29 09:33:24 2021 +0200

    tree-optimization/101242 - fix reverse graph entry detection

    This avoids detecting random unrelated nodes as possible entries
    to not backwards reachable regions of the SLP graph.  Instead
    explicitely add the problematic nodes.

    This temporary XFAILs gcc.dg/vect/pr67790.c until I get the
    permute propagation adjusted to when it needs more than one
    optimistic iteration.

    2021-06-29  Richard Biener  <rguenther@suse.de>

            PR tree-optimization/101242
            * tree-vect-slp.c (vect_slp_build_vertices): Force-add
            PHIs with not represented initial values as leafs.

            * gcc.dg/vect/bb-slp-pr101242.c: New testcase.
            * gcc.dg/vect/pr67790.c: XFAIL scan for zero VEC_PERM_EXPR.

  parent reply	other threads:[~2021-06-29  8:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-28 13:30 [Bug tree-optimization/101242] New: Segfault in SLP vectorizor after 2ad71efb5de jamborm at gcc dot gnu.org
2021-06-28 13:32 ` [Bug tree-optimization/101242] " jamborm at gcc dot gnu.org
2021-06-28 13:34 ` [Bug tree-optimization/101242] Segfault in SLP vectorizor after g:2ad71efb5de marxin at gcc dot gnu.org
2021-06-28 17:32 ` jamborm at gcc dot gnu.org
2021-06-28 21:40 ` dcb314 at hotmail dot com
2021-06-29  7:06 ` rguenth at gcc dot gnu.org
2021-06-29  7:51 ` dcb314 at hotmail dot com
2021-06-29  8:35 ` cvs-commit at gcc dot gnu.org [this message]
2021-06-29  8:35 ` rguenth at gcc dot gnu.org
2021-06-29  8:36 ` 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-101242-4-8q9FLqu9jV@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).