From: Darryl Dixon <esrever_otua@pythonhacker.is-a-geek.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Fedora 4 + GCC4 + Qemu WAS: [patch] gcc4 host support
Date: Fri, 17 Jun 2005 16:30:52 +1200 [thread overview]
Message-ID: <1118982652.12881.2.camel@unixadmindazfc2.chh.co.nz> (raw)
In-Reply-To: <200505121800.40417.paul@codesourcery.com>
Hi,
Fedora Core 4 with gcc4 seems to have some trouble compiling qemu,
even with the below patch attached. EG:
[...snip many signedness errors...]
gcc -Wall -O2 -g -fno-strict-aliasing -fomit-frame-pointer
-mpreferred-stack-boundary=2 -falign-functions=0 -fno-gcse
-fno-reorder-blocks -fno-optimize-sibling-calls -I.
-I/opt/src/qemu-snapshot-2005-06-15_23/target-i386
-I/opt/src/qemu-snapshot-2005-06-15_23 -D_GNU_SOURCE
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE
-I/opt/src/qemu-snapshot-2005-06-15_23/fpu
-I/opt/src/qemu-snapshot-2005-06-15_23/slirp -c -o
op.o /opt/src/qemu-snapshot-2005-06-15_23/target-i386/op.c
/opt/src/qemu-snapshot-2005-06-15_23/target-i386/ops_template_mem.h: In
function ‘op_cmpxchgb_kernel_T0_T1_EAX_cc’:
/opt/src/qemu-snapshot-2005-06-15_23/softmmu_header.h:184: error: can't
find a register in class ‘GENERAL_REGS’ while reloading ‘asm’
make[1]: *** [op.o] Error 1
make[1]: Leaving directory
`/opt/src/qemu-snapshot-2005-06-15_23/i386-softmmu'
make: *** [all] Error 1
[dixond@unixadmindazfc2 qemu-snapshot-2005-06-15_23]$ gcc --version
gcc (GCC) 4.0.0 20050519 (Red Hat 4.0.0-8)
Cheers,
D
On Thu, 2005-05-12 at 18:00 +0100, Paul Brook wrote:
> On Wednesday 11 May 2005 22:04, Paul Brook wrote:
> > The attached patch adds support for gcc4 x86 and x86_64 hosts.
>
> This time with the correct patch attached.
>
> Paul
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
--
Darryl Dixon <esrever_otua@pythonhacker.is-a-geek.net>
next prev parent reply other threads:[~2005-06-17 4:52 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-11 21:04 [Qemu-devel] [patch] gcc4 host support Paul Brook
2005-05-12 17:00 ` Paul Brook
2005-05-12 22:13 ` Pascal Terjan
2005-05-12 22:25 ` Paul Brook
2005-05-14 7:55 ` Filip Navara
2005-05-14 11:53 ` Paul Brook
2005-05-14 11:56 ` Filip Navara
2005-06-17 4:30 ` Darryl Dixon [this message]
2005-06-17 12:45 ` [Qemu-devel] Fedora 4 + GCC4 + Qemu WAS: " Paul Brook
[not found] ` <1119013084.5187.4.camel@darrylsfc3box>
2005-06-17 13:02 ` Paul Brook
2005-06-17 22:18 ` David Woodhouse
2005-06-20 1:18 ` Darryl Dixon
2005-05-16 9:41 ` [Qemu-devel] " David Woodhouse
2005-05-17 20:46 ` Paul Brook
2005-05-18 10:06 ` Herbert Poetzl
2005-05-18 16:02 ` Paul Brook
2005-05-18 16:10 ` David Woodhouse
2005-05-18 19:29 ` John Hogerhuis
2005-05-18 20:48 ` Paul Brook
2005-05-18 20:55 ` David Woodhouse
2005-05-18 21:16 ` Paul Brook
2005-05-18 21:29 ` jeebs
2005-05-18 22:37 ` Paul Brook
2005-05-18 23:05 ` Ian Rogers
2005-05-18 22:37 ` Ian Rogers
2005-05-19 7:23 ` Gwenole Beauchesne
2005-05-19 13:20 ` Paul Brook
2005-05-19 14:07 ` Gwenole Beauchesne
2005-05-19 15:44 ` Paul Brook
2005-05-19 18:14 ` Thomas Steffen
2005-05-19 18:52 ` Paul Brook
2005-05-19 19:38 ` Tim Walker
2005-05-19 19:45 ` Paul Brook
2005-05-19 21:03 ` Thomas Steffen
2005-05-19 22:25 ` John Hogerhuis
2005-05-20 9:59 ` Thomas Steffen
2005-05-20 12:57 ` Paul Brook
2005-05-19 16:18 ` Ian Rogers
2005-05-19 13:47 ` McMullan, Jason
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=1118982652.12881.2.camel@unixadmindazfc2.chh.co.nz \
--to=esrever_otua@pythonhacker.is-a-geek.net \
--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 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 NNTP newsgroup(s).