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 middle-end/55943] New: ICE in gen_reg_rtx Date: Fri, 11 Jan 2013 17:35:00 -0000 [thread overview] Message-ID: <bug-55943-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55943 Bug #: 55943 Summary: ICE in gen_reg_rtx Classification: Unclassified Product: gcc Version: 4.8.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: middle-end AssignedTo: unassigned@gcc.gnu.org ReportedBy: schwab@linux-m68k.org Target: ia64-*-* Created attachment 29150 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=29150 Testcase $ gcc-20130111/Build/gcc/xgcc -B gcc-20130111/Build/gcc/ -S gcc/gcc/testsuite/gcc.c-torture/compile/pr55921.c gcc/gcc/testsuite/gcc.c-torture/compile/pr55921.c: In function ‘foo’: gcc/gcc/testsuite/gcc.c-torture/compile/pr55921.c:21:1: internal compiler error: in gen_reg_rtx, at emit-rtl.c:866 } ^ 0x400000000040012f gen_reg_rtx(machine_mode) ../../gcc/emit-rtl.c:866 0x4000000000432f1f store_bit_field_1 ../../gcc/expmed.c:776 0x4000000000433b9f store_bit_field(rtx_def*, unsigned long, unsigned long, unsigned long, unsigned long, machine_mode, rtx_def*) ../../gcc/expmed.c:897 0x400000000045f40f write_complex_part ../../gcc/expr.c:2960 0x400000000045f6bf emit_move_complex_parts(rtx_def*, rtx_def*) ../../gcc/expr.c:3216 0x4000000000718dff gen_move_insn(rtx_def*, rtx_def*) ../../gcc/optabs.c:4783 0x40000000007f752f gen_reload ../../gcc/reload1.c:8705 0x40000000008077af emit_input_reload_insns ../../gcc/reload1.c:7591 0x40000000008077af do_input_reload ../../gcc/reload1.c:7877 0x40000000008077af emit_reload_insns ../../gcc/reload1.c:8069 0x40000000008077af reload_as_needed ../../gcc/reload1.c:4645 0x4000000000811f2f reload(rtx_def*, int) ../../gcc/reload1.c:1051 0x4000000000604caf do_reload ../../gcc/ira.c:4635 0x4000000000604caf rest_of_handle_reload ../../gcc/ira.c:4736 Note that this is the original version of pr55921.c with the matching constraints.
next reply other threads:[~2013-01-11 17:35 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-01-11 17:35 schwab@linux-m68k.org [this message] 2013-01-14 13:24 ` [Bug middle-end/55943] [4.8 Regression] " rguenth at gcc dot gnu.org 2013-01-14 15:45 ` [Bug middle-end/55943] [4.6/4.7/4.8 " jakub at gcc dot gnu.org 2013-02-07 21:13 ` aldyh at gcc dot gnu.org 2013-02-08 15:10 ` rguenth at gcc dot gnu.org 2013-03-16 13:18 ` [Bug middle-end/55943] [4.6/4.7/4.8/4.9 " danglin at gcc dot gnu.org 2013-03-16 13:20 ` danglin at gcc dot gnu.org 2013-03-22 14:42 ` jakub at gcc dot gnu.org 2013-05-31 10:58 ` [Bug middle-end/55943] [4.7/4.8/4.9 " jakub at gcc dot gnu.org 2013-10-16 9:48 ` jakub at gcc dot gnu.org 2014-03-27 1:04 ` danglin at gcc dot gnu.org 2014-05-22 9:01 ` [Bug middle-end/55943] [4.7/4.8/4.9/4.10 " rguenth at gcc dot gnu.org 2014-12-19 13:25 ` [Bug rtl-optimization/55943] [4.8/4.9/5 " jakub at gcc dot gnu.org 2015-06-23 8:14 ` [Bug rtl-optimization/55943] [4.8/4.9/5/6 " rguenth at gcc dot gnu.org 2015-06-26 19:52 ` [Bug rtl-optimization/55943] [4.9/5/6 " jakub at gcc dot gnu.org 2015-06-26 20:26 ` jakub 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-55943-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).