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 middle-end/109347] [lra] Spill failure for architecture without CC Date: Thu, 30 Mar 2023 19:47:19 +0000 [thread overview] Message-ID: <bug-109347-4-Kw2pexFooS@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109347-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109347 --- Comment #9 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Even for pre-LRA with reload in GCC 4.7.0: t.c: In function ‘f’: t.c:91:1: note: unable to find a register to spill in class ‘GR_REGS’ t.c:91:1: note: this is the insn: (insn 33 32 34 2 (set (reg:DI 198) (plus:DI (reg:DI 194 [ t9.0 ]) (const_int 1 [0x1]))) t.c:60 11 {*adddi3} (expr_list:REG_DEAD (reg:DI 194 [ t9.0 ]) (nil))) t.c:91:1: internal compiler error: in spill_failure, at reload1.c:2120 unrecognized DWARF version in .debug_info at 6 0x70e2bf _fatal_insn /bajas/pinskia/src/toolchain-47/scripts/../src/gcc/rtl-error.c:106 0x705bab spill_failure /bajas/pinskia/src/toolchain-47/scripts/../src/gcc/reload1.c:2120 0x705bab find_reload_regs /bajas/pinskia/src/toolchain-47/scripts/../src/gcc/reload1.c:2046 0x705bab select_reload_regs /bajas/pinskia/src/toolchain-47/scripts/../src/gcc/reload1.c:2066 0x705bab reload /bajas/pinskia/src/toolchain-47/scripts/../src/gcc/reload1.c:993 0x65fe6e do_reload /bajas/pinskia/src/toolchain-47/scripts/../src/gcc/ira.c:3733 0x65fe6e rest_of_handle_reload /bajas/pinskia/src/toolchain-47/scripts/../src/gcc/ira.c:3824 Please submit a full bug report, with preprocessed source if appropriate. Please include the complete backtrace with any bug report. So I am sure this is almost not a regression.
prev parent reply other threads:[~2023-03-30 19:47 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-30 18:59 [Bug middle-end/109347] New: " piggynl at outlook dot com 2023-03-30 18:59 ` [Bug middle-end/109347] " piggynl at outlook dot com 2023-03-30 19:32 ` pinskia at gcc dot gnu.org 2023-03-30 19:36 ` pinskia at gcc dot gnu.org 2023-03-30 19:38 ` pinskia at gcc dot gnu.org 2023-03-30 19:39 ` pinskia at gcc dot gnu.org 2023-03-30 19:40 ` pinskia at gcc dot gnu.org 2023-03-30 19:42 ` pinskia at gcc dot gnu.org 2023-03-30 19:42 ` pinskia at gcc dot gnu.org 2023-03-30 19:46 ` pinskia at gcc dot gnu.org 2023-03-30 19:47 ` pinskia at gcc dot gnu.org [this message]
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-109347-4-Kw2pexFooS@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).