All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thiemo Seufer <ths@networkno.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] sh4: more patches
Date: Fri, 22 Jun 2007 12:48:19 +0100	[thread overview]
Message-ID: <20070622114819.GD25967@networkno.de> (raw)
In-Reply-To: <aec7e5c30706220044u5b4ae7felc64ed595454ebb37@mail.gmail.com>

Magnus Damm wrote:
> Hi everyone,
> 
> Here comes a few more patches for the sh4 emulator. The should be
> applied on top of the patches that I posted a few weeks ago:
> 
> http://www.mail-archive.com/qemu-devel@nongnu.org/msg10830.html
> 
> Good news is that the user space emulator is in a much better shape
> now - with all the patches applied I'm successfully running a static
> busybox binary compiled for sh4 using qemu-sh4.
> 
> The method used to locate emulation bugs may be of value for other
> fellow qemu hackers. I've written a small gdb script that single steps
> in an endless loop dumping registers between each instruction. Then
> I've used this script on both real target hardware (using gdbserver)
> and using the gdbstub provided by qemu. Finally the traces have been
> compared. I have more patches for this if anyone is interested...
> 
> The patches attached in this email contain the following fixes:
> 
> - sh4: Emulate more fpu opcodes
> - sh4: Swap word order when accessing double floats

Doesn't this one also depend on the host endianness?


Thiemo

  reply	other threads:[~2007-06-22 11:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-22  7:44 [Qemu-devel] sh4: more patches Magnus Damm
2007-06-22 11:48 ` Thiemo Seufer [this message]
2007-06-25  6:42   ` Magnus Damm
2007-06-25 12:01     ` Thiemo Seufer
2007-07-04  4:19       ` Magnus Damm
2007-07-25  1:02         ` Paul Mundt
2007-06-25 15:28 ` Blue Swirl
2007-07-04  4:44   ` Magnus Damm
2007-07-04 18:01     ` Blue Swirl

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=20070622114819.GD25967@networkno.de \
    --to=ths@networkno.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.