public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/47369] New: [x32] internal compiler error: in extract_insn, at recog.c:2109
Date: Thu, 20 Jan 2011 04:14:00 -0000 [thread overview]
Message-ID: <bug-47369-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47369
Summary: [x32] internal compiler error: in extract_insn, at
recog.c:2109
Product: gcc
Version: 4.6.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: hjl.tools@gmail.com
On x32 branch, revision 169032 gave
[hjl@gnu-6 ilp32-9]$ cat z.i
struct FILE
{
int x;
};
extern struct FILE __sF[];
extern void bar (struct FILE *);
void dlmalloc_stats() {
bar ((&__sF[2]));
}
[hjl@gnu-6 ilp32-9]$ make z.s
/export/build/gnu/gcc-x32/build-x86_64-linux/gcc/xgcc
-B/export/build/gnu/gcc-x32/build-x86_64-linux/gcc/ -S -o z.s -mx32 -O2 -fPIC
-dp z.i
z.i: In function ‘dlmalloc_stats’:
z.i:9:1: error: unrecognizable insn:
(insn 5 4 6 3 (set (reg:SI 5 di)
(const:SI (plus:SI (symbol_ref:SI ("__sF") [flags 0x40] <var_decl
0x7f72be3d5000 __sF>)
(const_int 8 [0x8])))) z.i:8 -1
(nil))
z.i:9:1: internal compiler error: in extract_insn, at recog.c:2109
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
make: *** [z.s] Error 1
[hjl@gnu-6 ilp32-9]$
next reply other threads:[~2011-01-20 2:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-20 4:14 hjl.tools at gmail dot com [this message]
2011-01-20 5:28 ` [Bug target/47369] " hjl at gcc dot gnu.org
2011-07-26 18:04 ` uros at gcc dot gnu.org
2011-07-26 21:51 ` ubizjak at gmail dot com
2011-08-05 22:38 ` hjl 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-47369-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: 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).