public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "c at jia dot je" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/113033] New: GCC 14 (20231203 snapshot) ICE when building LSX vector rotate code on LoongArch
Date: Fri, 15 Dec 2023 16:44:29 +0000	[thread overview]
Message-ID: <bug-113033-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 113033
           Summary: GCC 14 (20231203 snapshot) ICE when building LSX
                    vector rotate code on LoongArch
           Product: gcc
           Version: 14.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: c at jia dot je
  Target Milestone: ---

Source code:

```
#include <lsxintrin.h>

v2u64 test(v2u64 a, int imm) {
  return (a << (imm & 63)) | (a >> (64 - (imm & 63)));
}

```

Command line to reproduce:

```
gcc-14 -mlsx -c test.c
```

Error message:

```
test.c: In function ‘test’:
test.c:5:1: error: unrecognizable insn:
    5 | }
      | ^
(insn 16 15 17 2 (set (reg:DI 92)
        (and:DI (neg:DI (reg:DI 80 [ _1 ]))
            (const_int 63 [0x3f]))) "test.c":4:28 -1
     (nil))
during RTL pass: vregs
test.c:5:1: internal compiler error: in extract_insn, at recog.cc:2804
0x5555591d419f internal_error(char const*, ...)
        ???:0
0x5555577b4d87 fancy_abort(char const*, int, char const*)
        ???:0
0x5555577998bb _fatal_insn(char const*, rtx_def const*, char const*, int, char
const*)
        ???:0
0x5555577998ef _fatal_insn_not_found(rtx_def const*, char const*, int, char
const*)
        ???:0
0x5555580704f7 extract_insn(rtx_insn*)
        ???:0
Please submit a full bug report, with preprocessed source (by using
-freport-bug).
Please include the complete backtrace with any bug report.
See <https://bugs.gentoo.org/> for instructions.
```

             reply	other threads:[~2023-12-15 16:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-15 16:44 c at jia dot je [this message]
2023-12-16 17:47 ` [Bug target/113033] " xry111 at gcc dot gnu.org
2023-12-16 18:16 ` xry111 at gcc dot gnu.org
2023-12-16 18:32 ` xry111 at gcc dot gnu.org
2023-12-16 18:44 ` xry111 at gcc dot gnu.org
2023-12-16 20:11 ` [Bug middle-end/113033] " xry111 at gcc dot gnu.org
2023-12-16 21:35 ` xry111 at gcc dot gnu.org
2023-12-18 13:47 ` xry111 at gcc dot gnu.org
2023-12-18 20:17 ` [Bug target/113033] " xry111 at gcc dot gnu.org
2023-12-18 20:34 ` xry111 at gcc dot gnu.org
2023-12-20 12:02 ` cvs-commit at gcc dot gnu.org
2023-12-20 12:05 ` xry111 at gcc dot gnu.org
2023-12-27 11:05 ` xry111 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-113033-4@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).