From: Tsuneo Saito <tsnsaito@gmail.com>
To: qemu-devel@nongnu.org
Cc: Tsuneo Saito <tsnsaito@gmail.com>
Subject: [Qemu-devel] [PATCH 0/4] SPARC64: Implement sparcv9 ldfa/stfa instructions
Date: Wed, 13 Jul 2011 12:30:45 +0900 [thread overview]
Message-ID: <1310527849-784-1-git-send-email-tsnsaito@gmail.com> (raw)
Hi,
This patch series implements sparcv9 stfa/ldfa instructions with
non block-transfer ASIs that implementations seem to be left unfinished.
This patch also adds fp_disabled exception checks on stfa/ldfa
as they are FP instructions.
target-sparc/op_helper.c | 31 ++++++++++++++++++++++---------
target-sparc/translate.c | 14 ++++++++++++--
2 files changed, 34 insertions(+), 11 deletions(-)
next reply other threads:[~2011-07-13 3:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-13 3:30 Tsuneo Saito [this message]
2011-07-13 3:30 ` [Qemu-devel] [PATCH 1/4] SPARC64: Implement ldfa/lddfa/ldqfa instructions properly Tsuneo Saito
2011-07-13 16:27 ` Blue Swirl
2011-07-13 18:02 ` Artyom Tarasenko
2011-07-13 18:19 ` Blue Swirl
2011-07-13 22:56 ` tsnsaito
2011-07-13 3:30 ` [Qemu-devel] [PATCH 2/4] SPARC64: fp_disabled checks on ldfa/lddfa/ldqfa Tsuneo Saito
2011-07-13 3:30 ` [Qemu-devel] [PATCH 3/4] SPARC64: Implement stfa/stdfa/stqfa instrcutions properly Tsuneo Saito
2011-07-13 3:30 ` [Qemu-devel] [PATCH 4/4] SPARC64: fp_disabled checks on stfa/stdfa/stqfa Tsuneo Saito
2011-07-13 8:57 ` [Qemu-devel] [PATCH 0/4] SPARC64: Implement sparcv9 ldfa/stfa instructions Artyom Tarasenko
2011-07-13 11:06 ` tsnsaito
2011-07-13 12:09 ` Mark Cave-Ayland
2011-07-13 12:48 ` tsnsaito
2011-07-13 16:34 ` Blue Swirl
2011-07-14 3:13 ` tsnsaito
2011-07-14 7:38 ` Artyom Tarasenko
2011-07-14 9:13 ` tsnsaito
2011-07-14 15:31 ` Blue Swirl
2011-07-15 1:55 ` tsnsaito
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=1310527849-784-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).