From: David Gibson <david@gibson.dropbear.id.au>
To: LemonBoy <thatlemon@gmail.com>
Cc: richard.henderson@linaro.org, qemu-ppc@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [PATCH v3 0/4] ppc/translate: Fix unordered f64/f128 comparisons
Date: Mon, 23 Nov 2020 17:08:54 +1100 [thread overview]
Message-ID: <20201123060854.GU521467@yekko.fritz.box> (raw)
In-Reply-To: <20201112230130.65262-1-thatlemon@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1014 bytes --]
On Fri, Nov 13, 2020 at 12:01:26AM +0100, LemonBoy wrote:
> Fix a couple of problems found in the emulation of f64/f128 comparisons plus
> some minimal self-contained commits to clean-up some code.
Applied to ppc-for-6.0.
As bug fixes, these could theoretically go into qemu-5.2. However,
since they're not regressions, I'm more comfortable delaying these to
6.0 given how late we are in the qemu-5.2 cycle.
>
> Giuseppe Musacchio (4):
> ppc/translate: Fix unordered f64/f128 comparisons
> ppc/translate: Turn the helper macros into functions
> ppc/translate: Delay NaN checking after comparison
> ppc/translate: Raise exceptions after setting the cc
>
> target/ppc/fpu_helper.c | 212 +++++++++++++++++++++++-----------------
> 1 file changed, 121 insertions(+), 91 deletions(-)
>
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2020-11-23 6:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-12 23:01 [PATCH v3 0/4] ppc/translate: Fix unordered f64/f128 comparisons LemonBoy
2020-11-12 23:01 ` [PATCH v3 1/4] " LemonBoy
2020-11-12 23:01 ` [PATCH v3 2/4] ppc/translate: Turn the helper macros into functions LemonBoy
2020-11-12 23:01 ` [PATCH v3 3/4] ppc/translate: Delay NaN checking after comparison LemonBoy
2020-11-12 23:01 ` [PATCH v3 4/4] ppc/translate: Raise exceptions after setting the cc LemonBoy
2020-11-23 6:08 ` David Gibson [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=20201123060854.GU521467@yekko.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=thatlemon@gmail.com \
/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).