public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "zhan3299 at purdue dot edu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug inline-asm/99015] New: ICE: Max. number of generated reload insns per insn is achieved (90) Date: Tue, 09 Feb 2021 01:32:36 +0000 [thread overview] Message-ID: <bug-99015-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99015 Bug ID: 99015 Summary: ICE: Max. number of generated reload insns per insn is achieved (90) Product: gcc Version: 10.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: inline-asm Assignee: unassigned at gcc dot gnu.org Reporter: zhan3299 at purdue dot edu Target Milestone: --- Another inline-asm issue causes an ICE. --- poc.c starts --- int main() { asm("" : : "fq"(.100)); } --- poc.c ends --- The version of GCC is 10.2.0 x86-64, and running 'gcc -O1 poc.c ' can trigger the ICE. --- error trace starts --- $ gcc -O1 poc.c during RTL pass: reload test.c: In function ‘main’: test.c:3:1: internal compiler error: maximum number of generated reload insns per insn achieved (90) 3 | } | ^ 0x9fb0c0 lra_constraints(bool) ../../gcc/gcc/lra-constraints.c:4952 0x9e9314 lra(_IO_FILE*) ../../gcc/gcc/lra.c:2440 0x9a7201 do_reload ../../gcc/gcc/ira.c:5523 0x9a7201 execute ../../gcc/gcc/ira.c:5709 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. --- error trace ends --- This issue only occurs when compiling with -O1 and higher, but does not with -O0. I also test other versions of GCC. It seems to affect GCC version 8.1 and higher, but not version 7.5 and lower. This issue may be similar with https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98991. However, as #98991 additionally affects GCC version 7.5 and lower, I suspect they are different.
next reply other threads:[~2021-02-09 1:32 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-09 1:32 zhan3299 at purdue dot edu [this message] 2021-02-12 19:14 ` [Bug inline-asm/99015] " zhan3299 at purdue dot edu 2021-09-14 7:17 ` [Bug rtl-optimization/99015] [9/10/11/12 Regression] " pinskia at gcc dot gnu.org 2022-01-21 13:18 ` rguenth at gcc dot gnu.org 2022-05-27 9:44 ` [Bug rtl-optimization/99015] [10/11/12/13 " rguenth at gcc dot gnu.org 2022-06-28 10:43 ` jakub at gcc dot gnu.org 2023-07-07 10:39 ` [Bug rtl-optimization/99015] [11/12/13/14 " rguenth at gcc dot gnu.org 2024-03-11 2:43 ` [Bug rtl-optimization/99015] [11/12/13 " law at gcc dot gnu.org 2024-05-08 11: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-99015-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: linkBe 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).