From: David Gibson <david@gibson.dropbear.id.au>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: G 3 <programmingkidx@gmail.com>,
"list@suse.de:PowerPC list:PowerPC" <qemu-ppc@nongnu.org>,
Eric Blake <eblake@redhat.com>,
qemu-devel qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [Qemu-ppc] How to add my implementation of the fmadds instruction to QEMU
Date: Thu, 29 Sep 2016 14:17:50 +1000 [thread overview]
Message-ID: <20160929041750.GN8390@umbus.fritz.box> (raw)
In-Reply-To: <CAFEAcA82dQbjKKrbYyp09wGkbTORvoHC1TqGfTjFFu-v8znuLw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1337 bytes --]
On Tue, Sep 27, 2016 at 09:58:02AM -0700, Peter Maydell wrote:
> On 27 September 2016 at 09:51, G 3 <programmingkidx@gmail.com> wrote:
> > The problem with your reasoning is you assume this instruction has to be
> > 100% correctly implemented. That every single "corner-case" has to be
> > accounted for.
>
> For upstream QEMU we've already made this design decision --
> emulation accuracy comes first, and speed is secondary.
> That's why we implement this the way we do.
I think there is a way you could get both speed and accuracy, but it's
a huge project:
You'd need to add full float awareness to TCG - so floating point TCG
values and floating point operations as tcp micro-ops, defined
according to IEEE semantics. Then you'd need to rewrite the TCG
frontends in terms of those new ops, at least for target CPUs close
enough to IEEE semantics for that to work. And you'd need to rewrite
the TCG backends to implement those fp ops in terms of host cpu fp
instructions .. at least when the host has fp behaviour close enough
to IEEE to make that work, with a fallback to soft float when that's
not the case.
--
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: 819 bytes --]
next prev parent reply other threads:[~2016-09-29 4:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-27 1:05 [Qemu-devel] How to add my implementation of the fmadds instruction to QEMU G 3
2016-09-27 3:41 ` [Qemu-devel] [Qemu-ppc] " David Gibson
2016-09-27 11:43 ` [Qemu-devel] " Peter Maydell
2016-09-27 14:33 ` G 3
2016-09-27 15:21 ` Peter Maydell
2016-09-27 16:16 ` Eric Blake
2016-09-27 16:51 ` G 3
2016-09-27 16:58 ` Peter Maydell
2016-09-29 4:17 ` David Gibson [this message]
2016-09-29 15:20 ` [Qemu-devel] [Qemu-ppc] " Programmingkid
2016-09-29 18:19 ` Alex Bennée
2016-09-29 21:52 ` Programmingkid
2016-09-29 22:36 ` Alex Bennée
2016-09-29 22:39 ` Programmingkid
2016-09-29 15:41 ` Peter Maydell
2016-09-29 16:55 ` Programmingkid
2016-09-30 0:39 ` David Gibson
2016-09-30 0:44 ` Programmingkid
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=20160929041750.GN8390@umbus.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=eblake@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=programmingkidx@gmail.com \
--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 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).