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/96974] [10/11 Regression] ICE in vect_get_vector_types_for_stmt compiling for SVE
Date: Thu, 25 Mar 2021 15:30:11 +0000	[thread overview]
Message-ID: <bug-96974-4-r1IXympUiZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96974-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #11 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Stam Markianos-Wright
<stammark@gcc.gnu.org>:

https://gcc.gnu.org/g:aac12084fc07319d5c8232c51dafa4e297bd5415

commit r11-7830-gaac12084fc07319d5c8232c51dafa4e297bd5415
Author: Stam Markianos-Wright <stam.markianos-wright@arm.com>
Date:   Thu Mar 25 15:29:41 2021 +0000

    tree-optimization/96974 - avoid ICE by replacing assert with standard
failure

    Minor patch to add a graceful exit in the rare case where an invalid
    combination of TYPE_VECTOR_SUBPARTS for nunits_vectype and
    *stmt_vectype_out is reached in vect_get_vector_types_for_stmt.

    This resolves the ICE seen in PR tree-optimization/96974, however the issue
    of correctly handling this rare vectorization combination is left for a
    later patch.

    Bootstrapped and reg-tested on aarch64-linux-gnu.

    2021-03-25  Stam Markianos-Wright  <stam.markianos-wright@arm.com>

    gcc/ChangeLog:

            PR tree-optimization/96974
            * tree-vect-stmts.c (vect_get_vector_types_for_stmt): Replace
assert
            with graceful exit.

    gcc/testsuite/ChangeLog:

            PR tree-optimization/96974
            * g++.target/aarch64/sve/pr96974.C: New test.

  parent reply	other threads:[~2021-03-25 15:30 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-08 11:20 [Bug tree-optimization/96974] New: " ktkachov at gcc dot gnu.org
2020-09-08 11:21 ` [Bug tree-optimization/96974] " ktkachov at gcc dot gnu.org
2020-09-08 13:03 ` rguenth at gcc dot gnu.org
2020-10-15 15:36 ` stammark at gcc dot gnu.org
2021-01-05 10:09 ` ktkachov at gcc dot gnu.org
2021-01-18 10:29 ` stammark at gcc dot gnu.org
2021-01-18 10:38 ` rsandifo at gcc dot gnu.org
2021-01-18 13:32 ` stammark at gcc dot gnu.org
2021-01-18 13:48 ` rsandifo at gcc dot gnu.org
2021-01-18 13:52 ` stammark at gcc dot gnu.org
2021-01-28 11:47 ` stammark at gcc dot gnu.org
2021-01-28 11:47 ` stammark at gcc dot gnu.org
2021-01-28 11:59 ` rsandifo at gcc dot gnu.org
2021-01-28 13:12 ` rguenth at gcc dot gnu.org
2021-03-25 15:30 ` cvs-commit at gcc dot gnu.org [this message]
2021-03-25 15:32 ` cvs-commit at gcc dot gnu.org
2021-03-31  9:42 ` ktkachov at gcc dot gnu.org
2021-03-31  9:54 ` rguenth at gcc dot gnu.org
2021-03-31 13:57 ` cvs-commit at gcc dot gnu.org
2021-03-31 13:59 ` 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-96974-4-r1IXympUiZ@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).