From: Stefan Weil <weil@mail.berlios.de>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] qemu/hw mips_malta.c mips_pica61.c mips_r4k.c
Date: Thu, 03 May 2007 22:41:42 +0200 [thread overview]
Message-ID: <463A4906.5060101@mail.berlios.de> (raw)
In-Reply-To: <E1Hhu8r-0006DY-Vf@cvs>
This workaround fixes the problems with QEMU and
Linux FPU emulation (at least in my tests):
Index: target-mips/helper.c
===================================================================
RCS file: /sources/qemu/qemu/target-mips/helper.c,v
retrieving revision 1.34
diff -u -b -B -r1.34 helper.c
--- target-mips/helper.c 13 Apr 2007 20:17:54 -0000 1.34
+++ target-mips/helper.c 3 May 2007 20:39:35 -0000
@@ -340,6 +340,7 @@
goto set_EPC;
case EXCP_AdEL:
cause = 4;
+ tb_flush(env);
goto set_EPC;
case EXCP_AdES:
cause = 5;
Of course, a better solution would be fixing self modifying code.
Stefan
Thiemo Seufer schrieb:
> CVSROOT: /sources/qemu
> Module name: qemu
> Changes by: Thiemo Seufer <ths> 07/04/28 21:07:41
>
> Modified files:
> hw : mips_malta.c mips_pica61.c mips_r4k.c
>
> Log message:
> Switch default CPU to 24Kf for now, as the Linux FPU emulation in
> the current qemu mips emulation fails in some cases. (The Linux
> FPU emulation works on real FPU-less hardware.)
>
> CVSWeb URLs:
> http://cvs.savannah.gnu.org/viewcvs/qemu/hw/mips_malta.c?cvsroot=qemu&r1=1.25&r2=1.26
> http://cvs.savannah.gnu.org/viewcvs/qemu/hw/mips_pica61.c?cvsroot=qemu&r1=1.2&r2=1.3
> http://cvs.savannah.gnu.org/viewcvs/qemu/hw/mips_r4k.c?cvsroot=qemu&r1=1.42&r2=1.43
prev parent reply other threads:[~2007-05-03 20:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-28 21:07 [Qemu-devel] qemu/hw mips_malta.c mips_pica61.c mips_r4k.c Thiemo Seufer
2007-05-03 20:41 ` Stefan Weil [this message]
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=463A4906.5060101@mail.berlios.de \
--to=weil@mail.berlios.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 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).