From: Thiemo Seufer <ths@networkno.de>
To: Magnus Damm <magnus.damm@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] sh4: further updates
Date: Sun, 13 May 2007 18:02:38 +0100 [thread overview]
Message-ID: <20070513170238.GD8380@networkno.de> (raw)
In-Reply-To: <aec7e5c30705090148j59bc5b27u5eb800b03e9baca3@mail.gmail.com>
Magnus Damm wrote:
> Hi everyone,
>
> Here comes the second batch of patches for the user space emulator.
> Below is a one line summary of each patch, please have a look in the
> patch header for details:
>
> - Fix XHACK() macro and use FREG if possible
> - Emulate more fpu opcodes
> - Document FPSCR usage
> - Use DREG() over XREG() if possible
> - Remove unnecessary pointer magic in shift operations
> - Add fpu register support to the gdb code
>
> If you have any questions or comments, please don't hesitate to contact me!
The sh4-fpu-new patch fails to build (on ppc/Linux) with:
gcc-3.4 -Wall -O2 -g -fno-strict-aliasing -I. -I.. -I/home/ths/qemu/qemu-write/target-sh4 -I/home/ths/qemu/qemu-write -D__powerpc__ -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -I/home/ths/qemu/qemu-write/fpu -I/home/ths/qemu/qemu-write/slirp -c -o translate-op.o /home/ths/qemu/qemu-write/translate-op.c
In file included from /home/ths/qemu/qemu-write/translate-op.c:36:
./op.h: In function `dyngen_code':
./op.h:1220: error: syntax error before ')' token
./op.h:1221: error: syntax error before ')' token
make[1]: *** [translate-op.o] Error 1
make[1]: Leaving directory `/home/ths/qemu/qemu-write/sh4-softmmu'
make: *** [subdir-sh4-softmmu] Error 2
Thiemo
next prev parent reply other threads:[~2007-05-13 17:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-09 8:48 [Qemu-devel] sh4: further updates Magnus Damm
2007-05-13 17:02 ` Thiemo Seufer [this message]
2007-05-14 9:01 ` Magnus Damm
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=20070513170238.GD8380@networkno.de \
--to=ths@networkno.de \
--cc=magnus.damm@gmail.com \
--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).