From: Magnus Damm <damm@opensource.se>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] sparc-user build error
Date: Sun, 10 Oct 2004 20:35:19 +0200 [thread overview]
Message-ID: <1097433319.15737.98.camel@kubu.opensource.se> (raw)
In-Reply-To: <416975A6.4030700@bellard.org>
Much better, thanks!
/ magnus
On Sun, 2004-10-10 at 19:47, Fabrice Bellard wrote:
> It should work now.
>
> Fabrice.
>
> Magnus Damm wrote:
> > Hello,
> >
> > I'm unable to build sparc-user on my powerpc box. I use gcc-3.4.1 from
> > Gentoo stable ppc, and I'm building the CVS version of QEMU.
> >
> > make[1]: Entering directory
> > `/home/damm/build/qemu/cvs/src/qemu/sparc-user'
> > gcc -Wall -O2 -g -fno-strict-aliasing -D__powerpc__ -I.
> > -I/home/damm/build/qemu/cvs/src/qemu/target-sparc
> > -I/home/damm/build/qemu/cvs/src/qemu
> > -I/home/damm/build/qemu/cvs/src/qemu/linux-user
> > -I/home/damm/build/qemu/cvs/src/qemu/linux-user/sparc -D_GNU_SOURCE
> > -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE
> > -I/home/damm/build/qemu/cvs/src/qemu/slirp -c -o exec.o
> > /home/damm/build/qemu/cvs/src/qemu/exec.c
> > gcc -Wall -O2 -g -fno-strict-aliasing -D__powerpc__ -I.
> > -I/home/damm/build/qemu/cvs/src/qemu/target-sparc
> > -I/home/damm/build/qemu/cvs/src/qemu
> > -I/home/damm/build/qemu/cvs/src/qemu/linux-user
> > -I/home/damm/build/qemu/cvs/src/qemu/linux-user/sparc -D_GNU_SOURCE
> > -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE
> > -I/home/damm/build/qemu/cvs/src/qemu/slirp -c -o translate-all.o
> > /home/damm/build/qemu/cvs/src/qemu/translate-all.c
> > In file included from
> > /home/damm/build/qemu/cvs/src/qemu/translate-all.c:41:
> > ./op.h: In function `dyngen_code':
> > ./op.h:4783: error: parse error before ')' token
> > ./op.h:4784: error: parse error before ')' token
> > ./op.h:4799: error: parse error before ')' token
> > ./op.h:4800: error: parse error before ')' token
> > make[1]: *** [translate-all.o] Error 1
> >
> > It seems to me that "op_fitos" and "op_fitod" in "target-sparc/op.c"
> > gets converted to wierd code in "sparc-user/op.h" by dyngen:
> >
> > op.c:
> >
> > void OPPROTO op_fitos(void)
> > {
> > FT0 = (float) *((int32_t *)&FT1);
> > }
> >
> > op.h:
> >
> > case INDEX_op_fitos: {
> > extern void op_fitos();
> > memcpy(gen_code_ptr, (void *)((char *)&op_fitos+0), 56);
> > *(uint16_t *)(gen_code_ptr + 18) = ((long)(&) + 0 + 0x8000) >> 16;
> > *(uint16_t *)(gen_code_ptr + 26) = ((long)(&) + 0);
> > gen_code_ptr += 56;
> > }
> > break;
> >
> > The same goes for "op_fitod". Look at the "(long)(&)", any ideas?
> >
> > / magnus
> >
> >
> >
> > _______________________________________________
> > Qemu-devel mailing list
> > Qemu-devel@nongnu.org
> > http://lists.nongnu.org/mailman/listinfo/qemu-devel
> >
> >
>
>
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
next prev parent reply other threads:[~2004-10-10 18:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-10 17:04 [Qemu-devel] sparc-user build error Magnus Damm
2004-10-10 17:47 ` Fabrice Bellard
2004-10-10 18:35 ` Magnus Damm [this message]
2004-10-10 17:50 ` Johannes Schindelin
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=1097433319.15737.98.camel@kubu.opensource.se \
--to=damm@opensource.se \
--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).