From: Tsuneo Saito <tsnsaito@gmail.com>
To: qemu-devel@nongnu.org
Cc: Tsuneo Saito <tsnsaito@gmail.com>
Subject: [Qemu-devel] [PATCH 0/2] SPARC64: implement %fprs register dirty bits
Date: Sat, 23 Jul 2011 11:20:05 +0900 [thread overview]
Message-ID: <1311387607-56720-1-git-send-email-tsnsaito@gmail.com> (raw)
Implement %fprs.DU/DL bits.
The FPU sets %fprs.DL and %fprs.DU when values are assigned to %f0-31
and %f32-63 respectively.
The first patch fixes problems that are found when adding the lines
for fprs and would be better to be fixed before adding the fprs thing.
Tsuneo Saito (2):
SPARC64: fix fnor* and fnand*
SPARC64: implement %fprs dirty bits
target-sparc/translate.c | 130 +++++++++++++++++++++++++++++++++++++++++++--
1 files changed, 124 insertions(+), 6 deletions(-)
--
1.7.5.4
next reply other threads:[~2011-07-23 2:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-23 2:20 Tsuneo Saito [this message]
2011-07-23 2:20 ` [Qemu-devel] [PATCH 1/2] SPARC64: fix fnor* and fnand* Tsuneo Saito
2011-07-23 2:20 ` [Qemu-devel] [PATCH 2/2] SPARC64: implement %fprs dirty bits Tsuneo Saito
2011-07-30 8:44 ` [Qemu-devel] [PATCH 0/2] SPARC64: implement %fprs register " 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=1311387607-56720-1-git-send-email-tsnsaito@gmail.com \
--to=tsnsaito@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).