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/113018] ICE in gimple_convert, gimple-fold.cc during the SLP pass
Date: Thu, 14 Dec 2023 15:57:20 +0000	[thread overview]
Message-ID: <bug-113018-4-4iwpaku557@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113018-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from GCC 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:4e9b2c94e45f5991a472fb639fb2baa6aa42b76b

commit r14-6552-g4e9b2c94e45f5991a472fb639fb2baa6aa42b76b
Author: Richard Biener <rguenther@suse.de>
Date:   Thu Dec 14 16:00:50 2023 +0100

    tree-optimization/113018 - ICE with BB reduction vectorization

    When BB reduction vectorization picks up a chain with an ASM def
    in it and that's inside the vectorized region we fail to get its
    LHS.  Instead of trying to get the correct def the following
    avoids vectorizing such def and instead keeps it as def to add
    in the epilog.

            PR tree-optimization/113018
            * tree-vect-slp.cc (vect_slp_check_for_roots): Only start
            SLP discovery from stmts with a LHS.

  parent reply	other threads:[~2023-12-14 15:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-14 10:20 [Bug tree-optimization/113018] New: " fkastl at suse dot cz
2023-12-14 14:04 ` [Bug tree-optimization/113018] " rguenth at gcc dot gnu.org
2023-12-14 14:27 ` rguenth at gcc dot gnu.org
2023-12-14 15:57 ` cvs-commit at gcc dot gnu.org [this message]
2023-12-14 15:57 ` 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-113018-4-4iwpaku557@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).