public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rsandifo 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: Mon, 18 Jan 2021 10:38:53 +0000	[thread overview]
Message-ID: <bug-96974-4-eqicXM27aN@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 #4 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> ---
(In reply to Stam Markianos-Wright from comment #3)
> Just started looking at this. I've narrowed it as the bug appearing with
> commit 9b75f56d4b7951c60a656396dddd4a65787b95bc.
> 
> I have yet to fire this up in gdb to see what's happening, but one test I
> did do was to try commenting out the assert that is causing the ICE and it
> then ran to completion. 
> 
> So one _total speculation_ would be that with these latest changes that
> enable groups of different sizes, this condition in the assert is now too
> strict:
> 
> 
> multiple_p (TYPE_VECTOR_SUBPARTS (nunits_vectype),
> 	    TYPE_VECTOR_SUBPARTS (*stmt_vectype_out)))
What are nunits_vectype and *stmt_vectype_out at the point
that the assert fails?

  parent reply	other threads:[~2021-01-18 10:38 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 [this message]
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
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-eqicXM27aN@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).