public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "schwab@linux-m68k.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/112918] [m68k] [LRA] ICE: maximum number of generated reload insns per insn achieved (90)
Date: Fri, 08 Dec 2023 19:37:04 +0000	[thread overview]
Message-ID: <bug-112918-4-1tHMJu77tV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112918-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from Andreas Schwab <schwab@linux-m68k.org> ---
spawn -ignore SIGHUP /daten/aranym/gcc/gcc-20231208/Build/gcc/xgcc
-B/daten/aranym/gcc/gcc-20231208/Build/gcc/
/daten/aranym/gcc/gcc-20231208/gcc/testsuite/gcc.dg/torture/vshuf-v16qi.c
-fdiagnostics-plain-output -O2 -lm -o ./vshuf-v16qi.exe
during RTL pass: reload
In file included from
/daten/aranym/gcc/gcc-20231208/gcc/testsuite/gcc.dg/torture/vshuf-v16qi.c:11:
/daten/aranym/gcc/gcc-20231208/gcc/testsuite/gcc.dg/torture/vshuf-main.inc: In
function 'test_3':
/daten/aranym/gcc/gcc-20231208/gcc/testsuite/gcc.dg/torture/vshuf-main.inc:27:1:
internal compiler error: maximum number of generated reload insns per insn
achieved (90)
/daten/aranym/gcc/gcc-20231208/gcc/testsuite/gcc.dg/torture/vshuf-16.inc:6:1:
note: in expansion of macro 'T'
/daten/aranym/gcc/gcc-20231208/gcc/testsuite/gcc.dg/torture/vshuf-main.inc:28:1:
note: in expansion of macro 'TESTS'
0xbe89f0 lra_constraints(bool)
        ../../gcc/lra-constraints.cc:5429
0xbcffba lra(_IO_FILE*, int)
        ../../gcc/lra.cc:2440
0xb7def7 do_reload
        ../../gcc/ira.cc:5973
0xb7def7 execute
        ../../gcc/ira.cc:6161

  parent reply	other threads:[~2023-12-08 19:37 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-08 10:53 [Bug target/112918] New: " schwab@linux-m68k.org
2023-12-08 13:07 ` [Bug target/112918] " rguenth at gcc dot gnu.org
2023-12-08 13:08 ` rguenth at gcc dot gnu.org
2023-12-08 13:32 ` schwab@linux-m68k.org
2023-12-08 13:36 ` schwab@linux-m68k.org
2023-12-08 14:30 ` schwab@linux-m68k.org
2023-12-08 19:34 ` schwab@linux-m68k.org
2023-12-08 19:37 ` schwab@linux-m68k.org [this message]
2023-12-11 10:12 ` rguenth at gcc dot gnu.org
2023-12-11 10:29 ` rguenth at gcc dot gnu.org
2023-12-11 10:44 ` rguenth at gcc dot gnu.org
2023-12-12  9:41 ` rguenth at gcc dot gnu.org
2023-12-15 20:17 ` vmakarov at gcc dot gnu.org
2023-12-18 22:15 ` cvs-commit at gcc dot gnu.org
2023-12-20  7:59 ` [Bug rtl-optimization/112918] " tschwinge at gcc dot gnu.org
2023-12-21 14:46 ` vmakarov at gcc dot gnu.org
2023-12-21 15:14 ` tschwinge at gcc dot gnu.org
2024-01-11 14:30 ` cvs-commit 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-112918-4-1tHMJu77tV@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).