From: Andreas Schwab <schwab@linux-m68k.org>
To: Alan Modra <amodra@gmail.com>
Cc: Bernd Schmidt <bschmidt@redhat.com>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] PR69195, Reload confused by invalid reg equivs
Date: Fri, 11 Mar 2016 20:40:00 -0000 [thread overview]
Message-ID: <877fh8ycip.fsf@linux-m68k.org> (raw)
In-Reply-To: <20160310091808.GO9617@bubble.grove.modra.org> (Alan Modra's message of "Thu, 10 Mar 2016 19:48:08 +1030")
I'm getting this crash on ia64 for gcc.c-torture/compile/pr58164.c:
Program received signal SIGSEGV, Segmentation fault.
0x40000000012286e0 in indirect_jump_optimize () at ../../gcc/ira.c:3865
3865 rtx_insn *def_insn = DF_REF_INSN (DF_REG_DEF_CHAIN (regno));
(gdb) bt
#0 0x40000000012286e0 in indirect_jump_optimize () at ../../gcc/ira.c:3865
#1 0x4000000001239570 in ira (f=0x0) at ../../gcc/ira.c:5188
#2 0x400000000123a6d0 in (anonymous namespace)::pass_ira::execute (
this=0x60000000002e2f50) at ../../gcc/ira.c:5539
Python Exception <type 'exceptions.AttributeError'> 'tuple' object has no attribute 'major':
#3 0x4000000001628ab0 in execute_one_pass (pass=) at ../../gcc/passes.c:2336
Python Exception <type 'exceptions.AttributeError'> 'tuple' object has no attribute 'major':
#4 0x4000000001629aa0 in execute_pass_list_1 (pass=)
at ../../gcc/passes.c:2410
Python Exception <type 'exceptions.AttributeError'> 'tuple' object has no attribute 'major':
#5 0x4000000001629bb0 in execute_pass_list_1 (pass=)
at ../../gcc/passes.c:2411
Python Exception <type 'exceptions.AttributeError'> 'tuple' object has no attribute 'major':
#6 0x4000000001629cf0 in execute_pass_list (fn=0x200000000104f0d8, pass=)
at ../../gcc/passes.c:2421
Python Exception <type 'exceptions.AttributeError'> 'tuple' object has no attribute 'major':
#7 0x4000000000917ee0 in cgraph_node::expand (this=)
at ../../gcc/cgraphunit.c:1980
#8 0x40000000009196c0 in output_in_order (no_reorder=false)
at ../../gcc/cgraphunit.c:2218
#9 0x4000000000923790 in symbol_table::compile (this=0x2000000000fb0000)
at ../../gcc/cgraphunit.c:2466
#10 0x4000000000926ae0 in symbol_table::finalize_compilation_unit (
this=0x2000000000fb0000) at ../../gcc/cgraphunit.c:2562
#11 0x4000000001a3ea80 in compile_file () at ../../gcc/toplev.c:490
#12 0x4000000001a44870 in do_compile () at ../../gcc/toplev.c:1988
#13 0x4000000001a45120 in toplev::main (this=0x600ffffffffef090, argc=2,
argv=0x600ffffffffef348) at ../../gcc/toplev.c:2096
#14 0x400000000318cad0 in main (argc=2, argv=0x600ffffffffef348)
at ../../gcc/main.c:39
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2016-03-11 20:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-04 14:54 [RFC] " Alan Modra
2016-03-04 17:40 ` Bernd Schmidt
2016-03-07 14:47 ` Alan Modra
2016-03-10 9:18 ` [PATCH] " Alan Modra
2016-03-10 9:48 ` Bernd Schmidt
2016-03-11 20:40 ` Andreas Schwab [this message]
2016-03-11 22:16 ` Alan Modra
2016-03-11 23:13 ` Alan Modra
2016-03-12 7:58 ` Jakub Jelinek
2016-03-12 8:26 ` Jeff Law
2016-03-12 9:07 ` Alan Modra
2016-03-12 9:29 ` Jakub Jelinek
2016-03-12 11:10 ` Richard Biener
2016-03-12 17:07 ` Jeff Law
2016-03-14 9:56 ` Richard Biener
2016-03-14 19:00 ` Jeff Law
2016-03-15 2:27 ` Alan Modra
2016-03-15 12:17 ` Bernd Schmidt
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=877fh8ycip.fsf@linux-m68k.org \
--to=schwab@linux-m68k.org \
--cc=amodra@gmail.com \
--cc=bschmidt@redhat.com \
--cc=gcc-patches@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).