public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "acoplan at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/99829] New: MVE: ICE in lra_assign at -O3
Date: Tue, 30 Mar 2021 13:19:38 +0000	[thread overview]
Message-ID: <bug-99829-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 99829
           Summary: MVE: ICE in lra_assign at -O3
           Product: gcc
           Version: 11.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: acoplan at gcc dot gnu.org
  Target Milestone: ---

The following fails:

$ arm-eabi-gcc -c -xc++ gcc/testsuite/c-c++-common/torture/vshuf-v16qi.c
-march=armv8.1-m.main+mve -mfloat-abi=hard -mtune=cortex-m7 -O3
during RTL pass: reload
In file included from gcc/testsuite/c-c++-common/torture/vshuf-v16qi.c:5:
gcc/testsuite/c-c++-common/torture/vshuf-main.inc: In function 'int main()':
gcc/testsuite/c-c++-common/torture/vshuf-main.inc:26:1: internal compiler
error: in lra_assign, at lra-assigns.c:1649
   26 | }
      | ^
0xe2d8fe lra_assign(bool&)
        /home/alecop01/toolchain/src/gcc/gcc/lra-assigns.c:1649
0xe298f2 lra(_IO_FILE*)
        /home/alecop01/toolchain/src/gcc/gcc/lra.c:2387
0xddb586 do_reload
        /home/alecop01/toolchain/src/gcc/gcc/ira.c:5835
0xddb586 execute
        /home/alecop01/toolchain/src/gcc/gcc/ira.c:6021
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.

On the GCC 10 branch, we ICE even without the -mtune option (the default
scheduling for MVE changed for GCC 11).

             reply	other threads:[~2021-03-30 13:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-30 13:19 acoplan at gcc dot gnu.org [this message]
2021-04-13  8:54 ` [Bug target/99829] " acoplan at gcc dot gnu.org
2024-03-12 15:40 ` thiago.bauermann at linaro dot org
2024-03-12 15:47 ` mkuvyrkov at gcc dot gnu.org
2024-03-12 16:16 ` vmakarov at gcc dot gnu.org
2024-03-12 17:03 ` mkuvyrkov at gcc dot gnu.org
2024-03-12 17:35 ` thiago.bauermann at linaro dot org
2024-03-13 15:34 ` vmakarov at gcc dot gnu.org
2024-03-19 20:59 ` cvs-commit at gcc dot gnu.org
2024-03-28 22:00 ` thiago.bauermann at linaro dot 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-99829-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).