From: Programmingkid <programmingkidx@gmail.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: Peter Maydell <peter.maydell@linaro.org>,
"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 20:44:28 -0400 [thread overview]
Message-ID: <D56AD6D3-6375-4662-BE6B-C0BAAC706FEF@gmail.com> (raw)
In-Reply-To: <20160930003957.GO30519@umbus.fritz.box>
On Sep 29, 2016, at 8:39 PM, David Gibson wrote:
> On Thu, Sep 29, 2016 at 12:55:23PM -0400, Programmingkid wrote:
>>
>> On Sep 29, 2016, at 11:41 AM, Peter Maydell wrote:
>>
>>> On 28 September 2016 at 21:17, David Gibson <david@gibson.dropbear.id.au> wrote:
>>>> 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.
>>>
>>> Also even if you have float support in both frontend and backend
>>> you still need to fall back to fully-emulated for the runtime
>>> corner cases (like where tininess before/after rounding makes a
>>> difference or where you need to care about minutiae of the
>>> floating point exception flags, etc). It's not impossible
>>> but it is a very large amount of technically complicated work.
>>
>>
>> This project sounds like it should have its own web page. Maybe even
>> its own Google Summer of Code entry. I created a mindmap of
>> this project. The picture is attached to this email. This is
>> just a start. Please let me know what should be added or changed.
>
> TBH, I think this is rather bigger than a GSoC project.
If it is really big, then it should be broken down into easier steps.
Any idea what those steps could be?
prev parent reply other threads:[~2016-09-30 0:53 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 ` [Qemu-devel] [Qemu-ppc] " David Gibson
2016-09-29 15:20 ` 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 [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=D56AD6D3-6375-4662-BE6B-C0BAAC706FEF@gmail.com \
--to=programmingkidx@gmail.com \
--cc=david@gibson.dropbear.id.au \
--cc=eblake@redhat.com \
--cc=peter.maydell@linaro.org \
--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).