public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/95272] ice in vectorizable_reduction, at tree-vect-loop.c:6197 since r11-564-g79f0451c67e8ed56
Date: Mon, 25 May 2020 08:57:49 +0000	[thread overview]
Message-ID: <bug-95272-4-iH9q1Sw7RN@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95272-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
static void
vect_slp_rearrange_stmts (slp_tree node, unsigned int group_size,
                          vec<unsigned> permutation,
                          hash_set<slp_tree> &visited)
{     
...
      /* ???  Computation nodes are isomorphic and need no rearrangement.
         This is a quick hack to cover those where rearrangement breaks
         semantics because only the first stmt is guaranteed to have the
         correct operation code due to others being swapped or inverted.  */
      stmt_vec_info first = SLP_TREE_SCALAR_STMTS (node)[0];
      if (is_gimple_assign (first->stmt)
          && gimple_assign_rhs_code (first->stmt) == COND_EXPR)
        return;

bites back.  This leaves us with an inconsistent SLP tree (harmless before
the change exposing the ICE).

  parent reply	other threads:[~2020-05-25  8:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-22 16:05 [Bug c++/95272] New: ice in vectorizable_reduction, at tree-vect-loop.c:6197 dcb314 at hotmail dot com
2020-05-25  6:59 ` [Bug tree-optimization/95272] " rguenth at gcc dot gnu.org
2020-05-25  8:57 ` rguenth at gcc dot gnu.org [this message]
2020-05-29 11:00 ` [Bug tree-optimization/95272] ice in vectorizable_reduction, at tree-vect-loop.c:6197 since r11-564-g79f0451c67e8ed56 cvs-commit at gcc dot gnu.org
2020-05-29 11:01 ` 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-95272-4-iH9q1Sw7RN@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).