public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/113221] [14 Regression][aarch64]ICE in extract_insn, at recog.cc:2812 since r14-6605-gc0911c6b357ba9
Date: Wed, 17 Jan 2024 00:10:14 +0000	[thread overview]
Message-ID: <bug-113221-4-eX00F2ZwYp@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113221-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #4)
> Actually `(match_operand 0 "register_operand")` should be used instead of
> the current `(match_code "reg,subreg")`.

Except that does not work since register_operand checks the mode ...
and then we fail to match:
```
(insn 46 45 47 2 (parallel [
            (set (reg:V4SI 148)
                (unspec:V4SI [
                        (mem/c:V2x16QI (reg:DI 147) [0 +0 S32 A128])
                    ] UNSPEC_LDP_FST))
            (set (reg:V4SI 149)
                (unspec:V4SI [
                        (mem/c:V2x16QI (reg:DI 147) [0 +0 S32 A128])
                    ] UNSPEC_LDP_SND))
        ]) "../../../libgcc/libgcov-interface.c":211:2 -1
     (nil))
```
Because we only define the load_pair_16 for TImode and TImode != V4SImode here
...

So Back to changing it to only test for reg and subreg of a reg then.

  parent reply	other threads:[~2024-01-17  0:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-03 18:07 [Bug target/113221] New: " mjires at suse dot cz
2024-01-03 18:09 ` [Bug target/113221] " pinskia at gcc dot gnu.org
2024-01-03 18:13 ` pinskia at gcc dot gnu.org
2024-01-03 18:13 ` pinskia at gcc dot gnu.org
2024-01-03 18:19 ` pinskia at gcc dot gnu.org
2024-01-08 12:52 ` jakub at gcc dot gnu.org
2024-01-16 23:24 ` pinskia at gcc dot gnu.org
2024-01-16 23:31 ` pinskia at gcc dot gnu.org
2024-01-17  0:10 ` pinskia at gcc dot gnu.org [this message]
2024-01-17  3:38 ` pinskia at gcc dot gnu.org
2024-01-17 22:03 ` cvs-commit at gcc dot gnu.org
2024-01-17 22:04 ` pinskia at gcc dot gnu.org
2024-01-18 15:26 ` acoplan 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-113221-4-eX00F2ZwYp@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).