public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "meadori at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/58595] internal compiler error: in gen_movsi when compiling on arm some files of lttng-tools with -fPIE
Date: Fri, 21 Feb 2014 19:13:00 -0000 [thread overview]
Message-ID: <bug-58595-4-xwRawP1kNc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-58595-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58595
Meador Inge <meadori at codesourcery dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |meadori at codesourcery dot com
--- Comment #2 from Meador Inge <meadori at codesourcery dot com> ---
I hit this problem as well. Here is a much reduced test case:
$ cat repro.c
struct state {
unsigned long last;
unsigned long current;
};
__thread struct state state;
void foo()
{
while (1) {
__sync_add_and_fetch_4(&state.current, (long) 1);
}
}
$ ./install/bin/arm-none-linux-gnueabi-gcc --version
arm-none-linux-gnueabi-gcc (GCC) 4.9.0 20140219 (experimental)
Copyright (C) 2014 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
meadori@build1-lucid-cs:/scratch/meadori/arm-none-linux-gnueabi-fsf-mainline$
./install/bin/arm-none-linux-gnueabi-gcc -fPIC -O2 repro.c
repro.c: In function 'foo':
repro.c:13:1: internal compiler error: in gen_movsi, at config/arm/arm.md:6272
}
^
0x8b3ee69 gen_movsi(rtx_def*, rtx_def*)
/scratch/meadori/arm-none-linux-gnueabi-fsf-mainline/src/gcc-mainline/gcc/config/arm/arm.md:6272
0x838853f insn_gen_fn::operator()(rtx_def*, rtx_def*) const
/scratch/meadori/arm-none-linux-gnueabi-fsf-mainline/src/gcc-mainline/gcc/recog.h:284
0x844b2be emit_move_insn_1(rtx_def*, rtx_def*)
/scratch/meadori/arm-none-linux-gnueabi-fsf-mainline/src/gcc-mainline/gcc/expr.c:3556
0x844b6f1 emit_move_insn(rtx_def*, rtx_def*)
/scratch/meadori/arm-none-linux-gnueabi-fsf-mainline/src/gcc-mainline/gcc/expr.c:3650
0x8508d4a process_insert_insn
/scratch/meadori/arm-none-linux-gnueabi-fsf-mainline/src/gcc-mainline/gcc/gcse.c:2133
0x85091f4 pre_edge_insert
/scratch/meadori/arm-none-linux-gnueabi-fsf-mainline/src/gcc-mainline/gcc/gcse.c:2310
0x8509c2a pre_gcse
/scratch/meadori/arm-none-linux-gnueabi-fsf-mainline/src/gcc-mainline/gcc/gcse.c:2641
0x8509d8a one_pre_gcse_pass
/scratch/meadori/arm-none-linux-gnueabi-fsf-mainline/src/gcc-mainline/gcc/gcse.c:2696
0x850caa4 execute_rtl_pre
/scratch/meadori/arm-none-linux-gnueabi-fsf-mainline/src/gcc-mainline/gcc/gcse.c:4127
0x850cba8 execute
/scratch/meadori/arm-none-linux-gnueabi-fsf-mainline/src/gcc-mainline/gcc/gcse.c:4186
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <http://gcc.gnu.org/bugs.html> for instructions.
next prev parent reply other threads:[~2014-02-21 19:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-02 19:12 [Bug target/58595] New: " yannick.brosseau at gmail dot com
2013-10-31 9:49 ` [Bug target/58595] " ramana at gcc dot gnu.org
2013-10-31 10:00 ` ramana at gcc dot gnu.org
2014-02-21 19:13 ` meadori at codesourcery dot com [this message]
2014-02-21 19:16 ` meadori at codesourcery dot com
2014-03-03 13:40 ` jakub at gcc dot gnu.org
2014-03-03 15:47 ` meadori at codesourcery dot com
2014-03-03 16:00 ` jakub at gcc dot gnu.org
2014-03-03 16:12 ` jakub at gcc dot gnu.org
2014-03-03 16:54 ` jakub at gcc dot gnu.org
2014-03-03 17:16 ` ktkachov at gcc dot gnu.org
2014-03-04 10:15 ` ktkachov at gcc dot gnu.org
2014-03-04 13:13 ` jakub at gcc dot gnu.org
2014-03-05 8:59 ` ktkachov at gcc dot gnu.org
2014-03-06 12:07 ` jakub at gcc dot gnu.org
2014-04-10 7:46 ` jakub at gcc dot gnu.org
2014-04-10 8:03 ` 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-58595-4-xwRawP1kNc@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: 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).