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/47725] New: [x32] error: unable to find a register to spill in class DIREG
Date: Mon, 14 Feb 2011 01:07:00 -0000 [thread overview]
Message-ID: <bug-47725-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47725
Summary: [x32] error: unable to find a register to spill in
class DIREG
Product: gcc
Version: 4.6.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: hjl.tools@gmail.com
CC: ubizjak@gmail.com
On x32 branch, I got
/export/build/gnu/gcc-x32/build-x86_64-linux/gcc/xgcc
-B/export/build/gnu/gcc-x32/build-x86_64-linux/gcc/ -S -o u.s -mx32 -O2 -g
-fPIC u.c
u.c: In function \u2018__frame_state_for\u2019:
u.c:14:1: error: unable to find a register to spill in class \u2018DIREG\u2019
u.c:14:1: error: this is the insn:
(insn 11 20 14 2 (parallel [
(set (reg:DI 2 cx [64])
(const_int 0 [0]))
(set (reg/f:DI 0 ax [62])
(plus:DI (ashift:DI (reg:DI 2 cx [64])
(const_int 3 [0x3]))
(reg/f:DI 1 dx [60])))
(set (mem/s/c:BLK (reg/f:DI 1 dx [60]) [0 context+0 S72 A64])
(const_int 0 [0]))
(use (reg:DI 0 ax [63]))
(use (reg:DI 2 cx [64]))
]) u.c:11 874 {*rep_stosdi_rex64}
(expr_list:REG_DEAD (reg:DI 0 ax [63])
(expr_list:REG_UNUSED (reg:DI 2 cx [64])
(expr_list:REG_UNUSED (reg/f:DI 0 ax [62])
(nil)))))
u.c:14:1: internal compiler error: in spill_failure, at reload1.c:2105
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
make: *** [u.s] Error 1
[hjl@gnu-6 ilp32-14]$
next reply other threads:[~2011-02-14 0:46 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-14 1:07 hjl.tools at gmail dot com [this message]
2011-02-14 1:08 ` [Bug target/47725] " hjl.tools at gmail dot com
2011-02-14 1:31 ` hjl.tools at gmail dot com
2011-02-14 3:18 ` [Bug middle-end/47725] " hjl.tools at gmail dot com
2011-02-14 8:16 ` ebotcazou at gcc dot gnu.org
2011-02-14 14:08 ` hjl.tools at gmail dot com
2011-02-14 14:21 ` hjl.tools at gmail dot com
2011-02-14 19:01 ` hjl at gcc dot gnu.org
2011-02-14 19:43 ` hjl.tools at gmail dot com
2011-02-15 17:28 ` hjl at gcc dot gnu.org
2011-02-15 20:30 ` hjl at gcc dot gnu.org
2011-02-16 20:22 ` hjl at gcc dot gnu.org
2011-03-18 0:45 ` hjl at gcc dot gnu.org
2011-03-18 5:00 ` hjl at gcc dot gnu.org
2011-04-02 6:04 ` hjl at gcc dot gnu.org
2011-04-02 6:05 ` hjl at gcc dot gnu.org
2011-06-20 14:54 ` hjl at gcc dot gnu.org
2011-06-20 16:02 ` ebotcazou at gcc dot gnu.org
2011-06-20 17:04 ` hjl at gcc dot gnu.org
2011-07-22 6:02 ` pbone at csse dot unimelb.edu.au
2011-07-22 6:07 ` pbone at csse dot unimelb.edu.au
2011-07-28 17:03 ` ubizjak at gmail dot com
2011-07-28 17:07 ` ubizjak 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-47725-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).