public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "enrico.scholz at informatik dot tu-chemnitz.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/56732] ICE in advance_target_bb
Date: Tue, 30 Apr 2013 12:07:00 -0000 [thread overview]
Message-ID: <bug-56732-4-4D8IDJSOkn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56732-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56732
enrico.scholz at informatik dot tu-chemnitz.de changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |enrico.scholz at informatik
| |dot tu-chemnitz.de
--- Comment #5 from enrico.scholz at informatik dot tu-chemnitz.de 2013-04-30 12:07:46 UTC ---
I can reproduce this error message with gcc-4.8 (patched by OpenEmbedded) on an
ARM platform with a simple
----
extern void bar();
void __attribute__((__naked__)) foo(void)
{
bar();
}
----
$ arm-linux-gnueabi-gcc -O2 -c /tmp/xxx.c
/tmp/xxx.c: In function 'foo':
/tmp/xxx.c:5:1: internal compiler error: in advance_target_bb, at
sched-rgn.c:3552
next prev parent reply other threads:[~2013-04-30 12:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-25 22:48 [Bug c/56732] New: ICE diffgeom at gmail dot com
2013-03-26 9:40 ` [Bug rtl-optimization/56732] ICE in advance_target_bb mikpe at it dot uu.se
2013-03-26 13:35 ` mikpe at it dot uu.se
2013-03-26 14:24 ` rguenth at gcc dot gnu.org
2013-04-26 12:25 ` gretay at gcc dot gnu.org
2013-04-30 12:07 ` enrico.scholz at informatik dot tu-chemnitz.de [this message]
2013-05-01 17:32 ` gretay at gcc dot gnu.org
2013-05-24 15:18 ` gretay at gcc dot gnu.org
2013-05-24 15:19 ` gretay at gcc dot gnu.org
2013-05-31 15:31 ` diffgeom at gmail dot com
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-56732-4-4D8IDJSOkn@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).