From: felix-qemu@fefe.de
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] qemu CVS HEAD does not compile with gcc 3.4
Date: Thu, 24 Jun 2004 11:30:57 +0200 [thread overview]
Message-ID: <20040624093057.GA24898@codeblau.de> (raw)
Here's what happens:
make[1]: Entering directory `/cvs/qemu/i386'
gcc -Wall -O2 -g -fno-strict-aliasing -fomit-frame-pointer -mpreferred-stack-boundary=2 -falign-functions=0 -fno-reorder-blocks -fno-optimize-sibling-calls -I. -I/cvs/qemu/target-i386 -I/cvs/qemu -D_GNU_SOURCE -I/cvs/qemu/slirp -c -o op.o /cvs/qemu/target-i386/op.c
/cvs/qemu/target-i386/ops_template_mem.h: In function `op_rolb_kernel_T0_T1_cc':
/cvs/qemu/softmmu_header.h:179: error: can't find a register in class `GENERAL_REGS' while reloading `asm'
make[1]: *** [op.o] Error 1
make[1]: Leaving directory `/cvs/qemu/i386'
gmake: *** [all] Error 1
It's the function "glue", which is static inline, but still uses ebp. Huh?
We are compiling -fomit-frame-pointer...?
The function spills eax, ecx and edx, takes two register arguments and two
memory location arguments. Apparently, gcc 3.4 wants to put the memory
locations into registers as well...?
Felix
next reply other threads:[~2004-06-24 9:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-24 9:30 felix-qemu [this message]
2004-06-24 6:12 ` [Qemu-devel] qemu CVS HEAD does not compile with gcc 3.4 Jani Monoses
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=20040624093057.GA24898@codeblau.de \
--to=felix-qemu@fefe.de \
--cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.