public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/114801] [14/15 Regression] arm: ICE in find_cached_value, at rtx-vector-builder.cc:100 with MVE intrinsics
Date: Fri, 26 Apr 2024 14:17:17 +0000	[thread overview]
Message-ID: <bug-114801-4-Uq9ZJI0stO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114801-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #9 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Christophe Lyon from comment #7)
> This fails because down the call chain from lowpart_subreg, we reach
> gcc_unreachable in rtx_vector_builder::find_cached_value because m_mode ==
> V4BImode (so is MODE_VECTOR_BOOL), but is not a valid expected boolean
> constant vector.

Ah, so the builtin prototype says the argument is unsigned short (or unsigned
char?)
but mode (as the insn predicate mode) is V*BImode in that case?
Then it would still be passed as SImode, so one would need
if (GET_MODE (x) == SImode || GET_MODE (x) == VOIDmode)
  {
    x = lowpart_subreg ((mode == HImode || mode == V16BImode) ? HImode :
QImode, x, SImode);
    if (mode != HImode)
      x = lowpart_subreg (mode, x, mode == V16BImode ? HImode : QImode);
  }
Does that second lowpart_subreg create CONST_VECTOR you are looking for?

  parent reply	other threads:[~2024-04-26 14:17 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-22 10:45 [Bug target/114801] New: [14 " acoplan at gcc dot gnu.org
2024-04-22 16:21 ` [Bug target/114801] " clyon at gcc dot gnu.org
2024-04-22 18:12 ` jakub at gcc dot gnu.org
2024-04-22 19:26 ` rguenth at gcc dot gnu.org
2024-04-26 13:14 ` [Bug target/114801] [14/15 " clyon at gcc dot gnu.org
2024-04-26 13:26 ` jakub at gcc dot gnu.org
2024-04-26 13:51 ` jakub at gcc dot gnu.org
2024-04-26 13:52 ` jakub at gcc dot gnu.org
2024-04-26 13:59 ` clyon at gcc dot gnu.org
2024-04-26 14:12 ` clyon at gcc dot gnu.org
2024-04-26 14:17 ` jakub at gcc dot gnu.org [this message]
2024-04-26 14:18 ` jakub at gcc dot gnu.org
2024-04-26 15:00 ` jakub at gcc dot gnu.org
2024-04-26 17:36 ` clyon at gcc dot gnu.org
2024-04-26 18:02 ` jakub at gcc dot gnu.org
2024-04-26 21:06 ` clyon at gcc dot gnu.org
2024-04-26 21:21 ` jakub at gcc dot gnu.org
2024-04-26 23:11 ` clyon at gcc dot gnu.org
2024-04-29 11:49 ` avieira at gcc dot gnu.org
2024-04-29 11:52 ` avieira at gcc dot gnu.org
2024-04-29 13:41 ` clyon at gcc dot gnu.org
2024-04-29 13:51 ` jakub at gcc dot gnu.org
2024-04-29 13:56 ` jakub at gcc dot gnu.org
2024-04-29 14:07 ` clyon at gcc dot gnu.org
2024-04-29 14:11 ` jakub at gcc dot gnu.org
2024-04-29 15:39 ` jakub at gcc dot gnu.org
2024-04-29 15:52 ` jakub at gcc dot gnu.org
2024-04-29 15:56 ` clyon at gcc dot gnu.org
2024-04-29 16:01 ` clyon at gcc dot gnu.org
2024-04-29 16:06 ` jakub at gcc dot gnu.org
2024-04-29 16:07 ` jakub at gcc dot gnu.org
2024-04-29 16:15 ` clyon at gcc dot gnu.org
2024-04-29 16:48 ` jakub at gcc dot gnu.org
2024-05-06 17:32 ` clyon at gcc dot gnu.org
2024-05-06 17:51 ` jakub at gcc dot gnu.org
2024-05-07  7:45 ` 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-114801-4-Uq9ZJI0stO@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).