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 target/105394] [12/13 Regression] ICE: verify_gimple failed with MVE during GIMPLE pass: veclower2
Date: Fri, 29 Apr 2022 09:07:54 +0000	[thread overview]
Message-ID: <bug-105394-4-baXWejW3vf@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105394-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> ---
I think the fix should rather be to the

      else 
        aa = tree_vec_extract (gsi, cond_type, a, width, index);

part which assumes that if a is not a comparison or a integer mode mask then
the mask vector element width is the same as the data element width which
isn't the case for VnBImode vectors (neither on MVE which can have multi-bit
bitsize BImode elements nor on SVE/GCN which I think have one-bit bitsize
BImode elements only).

  parent reply	other threads:[~2022-04-29  9:07 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-26 12:23 [Bug tree-optimization/105394] New: [12 " acoplan at gcc dot gnu.org
2022-04-26 12:40 ` [Bug tree-optimization/105394] " rguenth at gcc dot gnu.org
2022-04-26 12:42 ` acoplan at gcc dot gnu.org
2022-04-26 13:18 ` rguenth at gcc dot gnu.org
2022-04-26 13:19 ` rguenth at gcc dot gnu.org
2022-04-26 13:22 ` [Bug target/105394] " rguenth at gcc dot gnu.org
2022-04-29  9:07 ` rguenth at gcc dot gnu.org [this message]
2022-04-29  9:20 ` [Bug target/105394] [12/13 " rguenth at gcc dot gnu.org
2022-04-29  9:57 ` rguenth at gcc dot gnu.org
2022-04-29  9:59 ` acoplan at gcc dot gnu.org
2022-05-03  8:34 ` acoplan at gcc dot gnu.org
2022-05-03  8:49 ` rguenther at suse dot de
2022-05-03  9:19 ` cvs-commit at gcc dot gnu.org
2022-05-03  9:25 ` [Bug target/105394] [12 " rguenth at gcc dot gnu.org
2022-05-06  8:33 ` jakub at gcc dot gnu.org
2022-05-06  9:27 ` cvs-commit at gcc dot gnu.org
2022-05-06  9:28 ` 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-105394-4-baXWejW3vf@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).