public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bernds at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/52425] [4.6 Regression] ICE when compiling file from audacious on debian sparc Date: Fri, 02 Mar 2012 14:24:00 -0000 [thread overview] Message-ID: <bug-52425-4-W8HppcxvQG@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-52425-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52425 --- Comment #4 from Bernd Schmidt <bernds at gcc dot gnu.org> 2012-03-02 14:22:54 UTC --- For some reason I can never reproduce sparc bugs with cross compilers. The original testcase doesn't fail here; the reduced one fails but with a different error message, and it fails in instantiate_virtual_regs which is before any head-merging ever runs: sparcbug.i: In function ‘action_button_cb’: sparcbug.i:57:1: error: unrecognizable insn: (insn 7 6 8 3 (set (reg:SI 130) (lo_sum:SI (reg:SI 130) (unspec:SI [ (symbol_ref/f:DI ("*.LC0") [flags 0x2] <var_decl 0x7ffff6cd7f00 *.LC0>) ] 0))) sparcbug.i:49 -1 (nil)) Breakpoint 2, internal_error (gmsgid=0xd6093d "in %s, at %s:%d") at ../../trunk/gcc/diagnostic.c:839 839 { (gdb) bt #0 internal_error (gmsgid=0xd6093d "in %s, at %s:%d") at ../../trunk/gcc/diagnostic.c:839 #1 0x0000000000bcf7cc in fancy_abort (file=<optimized out>, line=2123, function=0xc99260 "extract_insn") at ../../trunk/gcc/diagnostic.c:899 #2 0x000000000081e8d3 in _fatal_insn (msgid=<optimized out>, insn=0x7ffff6bc5990, file=0xc9885b "../../trunk/gcc/recog.c", line=2123, function=0xc99260 "extract_insn") at ../../trunk/gcc/rtl-error.c:110 #3 0x000000000081e912 in _fatal_insn_not_found (insn=0xc99260, file=0xc9886b "recog.c", line=2123, function=0xa <Address 0xa out of bounds>) at ../../trunk/gcc/rtl-error.c:118 #4 0x00000000007ea2b4 in extract_insn (insn=0x7ffff6bc5990) at ../../trunk/gcc/recog.c:2123 #5 0x00000000006cfe1c in instantiate_virtual_regs_in_insn (insn=0x7ffff6bc5990) at ../../trunk/gcc/function.c:1555 #6 instantiate_virtual_regs () at ../../trunk/gcc/function.c:1911 Please post the actual command line that gets passed to cc1. Also, it would be helpful if you could load cc1 into a debugger and do the following at the crash site in output_addr_const: (gdb) p debug_rtx (x) and at some higher level, also use debug_rtx to print out the insn it's trying to print.
next prev parent reply other threads:[~2012-03-02 14:24 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-02-28 22:55 [Bug c/52425] New: " plugwash at p10link dot net 2012-02-29 9:14 ` [Bug target/52425] [4.6 Regression] " rguenth at gcc dot gnu.org 2012-02-29 12:43 ` mikpe at it dot uu.se 2012-02-29 15:57 ` mikpe at it dot uu.se 2012-02-29 19:52 ` mikpe at it dot uu.se 2012-03-02 14:24 ` bernds at gcc dot gnu.org [this message] 2012-03-02 16:22 ` mikpe at it dot uu.se 2012-03-03 12:06 ` [Bug target/52425] [4.6 Regression] ICE when compiling file from audacious with -fPIC -g ebotcazou at gcc dot gnu.org 2012-03-03 13:45 ` ebotcazou at gcc dot gnu.org 2012-03-03 13:48 ` ebotcazou 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-52425-4-W8HppcxvQG@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).