From: James Clarke <jrtc27@jrtc27.com>
To: qemu-devel@nongnu.org
Cc: James Clarke <jrtc27@jrtc27.com>,
qemu-ppc@nongnu.org, david@gibson.dropbear.id.au
Subject: [Qemu-devel] [PATCH v2 0/2] PPC handles mcrfs incorrectly
Date: Fri, 29 Jan 2016 18:40:19 +0000 [thread overview]
Message-ID: <1454092821-46795-1-git-send-email-jrtc27@jrtc27.com> (raw)
The first commit is because some FP_ macros needed to calculate
FP_EX_CLEAR_BITS did not exist, and I reordered all the FP_ macros so that they
are defined in the same order as the FPSCR_ macros. This has not changed since
the previous version.
The second commit stops bits in the FPSCR being cleared when read from with
mcrfs which shouldn't be, which includes the rounding mode being cleared by the
act of reading the current rounding mode. This has changed since the last
version to address compiler warnings; I don't actually know how it worked given
the warnings issued, but apologies for submitting such a broken patch.
James Clarke (2):
target-ppc: Make every FPSCR_ macro have a corresponding FP_ macro
target-ppc: mcrfs should always update FEX/VX and only clear exception
bits
target-ppc/cpu.h | 37 ++++++++++++++++++++++++++++---------
target-ppc/translate.c | 21 +++++++++++++++++----
2 files changed, 45 insertions(+), 13 deletions(-)
--
2.7.0
next reply other threads:[~2016-01-29 18:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-29 18:40 James Clarke [this message]
2016-01-29 18:40 ` [Qemu-devel] [PATCH v2 1/2] target-ppc: Make every FPSCR_ macro have a corresponding FP_ macro James Clarke
2016-01-29 18:40 ` [Qemu-devel] [PATCH v2 2/2] target-ppc: mcrfs should always update FEX/VX and only clear exception bits James Clarke
2016-01-31 23:50 ` David Gibson
2016-02-01 0:04 ` James Clarke
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=1454092821-46795-1-git-send-email-jrtc27@jrtc27.com \
--to=jrtc27@jrtc27.com \
--cc=david@gibson.dropbear.id.au \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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.