From: Steve Ellcey <sellcey@cavium.com>
To: Christophe Lyon <christophe.lyon@linaro.org>,
James Greenhalgh <james.greenhalgh@arm.com>
Cc: Wilco Dijkstra <Wilco.Dijkstra@arm.com>,
GCC Patches <gcc-patches@gcc.gnu.org>, nd <nd@arm.com>
Subject: Re: [PATCH][AArch64] Fix ICE due to store_pair_lanes
Date: Thu, 30 Nov 2017 00:52:00 -0000 [thread overview]
Message-ID: <1511998508.7649.27.camel@cavium.com> (raw)
In-Reply-To: <1511994409.7649.24.camel@cavium.com>
FYI: Here is a cut down test case showing the failure:
int foo (void) { }
extern void plunk ();
int splat (void)
{
      static int once = 0;
      plunk (&once, foo);
}
% obj/gcc/gcc/cc1 -mabi=ilp32 -O2 -quiet x.i
during RTL pass: final
x.i: In function âsplatâ:
x.i:7:1: internal compiler error: in aarch64_print_address_internal, at config/aarch64/aarch64.c:5638
 }
 ^
0x14286c7 aarch64_print_address_internal
/home/sellcey/gcc-spec-
ilp32/src/gcc/gcc/config/aarch64/aarch64.c:5638
0x1428d4b aarch64_print_operand_address
/home/sellcey/gcc-spec-
ilp32/src/gcc/gcc/config/aarch64/aarch64.c:5735
0xb5fa93 output_address(machine_mode, rtx_def*)
/home/sellcey/gcc-spec-ilp32/src/gcc/gcc/final.c:3905
0xb5f40b output_asm_insn(char const*, rtx_def**)
/home/sellcey/gcc-spec-ilp32/src/gcc/gcc/final.c:3766
0xb5e0df final_scan_insn(rtx_insn*, _IO_FILE*, int, int, int*)
/home/sellcey/gcc-spec-ilp32/src/gcc/gcc/final.c:3064
0xb5bfbb final(rtx_insn*, _IO_FILE*, int)
/home/sellcey/gcc-spec-ilp32/src/gcc/gcc/final.c:2052
0xb60d27 rest_of_handle_final
/home/sellcey/gcc-spec-ilp32/src/gcc/gcc/final.c:4490
0xb6110f execute
/home/sellcey/gcc-spec-ilp32/src/gcc/gcc/final.c:4564
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.
prev parent reply other threads:[~2017-11-29 23:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-27 15:44 Wilco Dijkstra
2017-11-28 18:40 ` James Greenhalgh
2017-11-29 21:03 ` Christophe Lyon
2017-11-29 22:32 ` Steve Ellcey
2017-11-30 0:52 ` Steve Ellcey [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=1511998508.7649.27.camel@cavium.com \
--to=sellcey@cavium.com \
--cc=Wilco.Dijkstra@arm.com \
--cc=christophe.lyon@linaro.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=james.greenhalgh@arm.com \
--cc=nd@arm.com \
/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).