From: Peter Maydell <peter.maydell@linaro.org>
To: G 3 <programmingkidx@gmail.com>
Cc: "list@suse.de:PowerPC list:PowerPC" <qemu-ppc@nongnu.org>,
qemu-devel qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] How to add my implementation of the fmadds instruction to QEMU
Date: Tue, 27 Sep 2016 08:21:08 -0700 [thread overview]
Message-ID: <CAFEAcA8Hg4BrP=CqQLCmyu8ysEADqUoSuhA0_WVM9ch2tb3aHw@mail.gmail.com> (raw)
In-Reply-To: <F705365A-5746-44BA-B820-33A4A993EDDD@gmail.com>
On 27 September 2016 at 07:33, G 3 <programmingkidx@gmail.com> wrote:
>
> On Sep 27, 2016, at 7:43 AM, Peter Maydell wrote:
>> In particular, for fmadds, it is important that there
>> is no intermediate rounding done between the multiply
>> and the addition. This means that you need to effectively
>> do the multiply and the addition at a higher precision than
>> the input arguments, so simple multiplication and addition
>> of floats will give you wrong answers.
>
>
> It sounds like I should change my argument types to double.
That will fix only a very tiny part of the problem.
You will also need to get right floating point exception flags,
handling of subnormal numbers, and various other implementation
specifics of IEEE.
> I still want to try implementing this function. I'm thinking
> rewriting the helper_fmadd() function in target-ppc/fpu_helper.c.
> Does that sound correct?
That's the place that would need to be reimplemented.
I recommend doing very thorough testing by feeding the
instruction a lot of randomly selected input values and
comparing the output value and the output floating point
status/exception flags against the current implementation
and/or real hardware.
I really think you'll find that this is just impossible
to implement correctly with the host compiler's floating
point C expressions, though.
thanks
-- PMM
next prev parent reply other threads:[~2016-09-27 15:21 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 [this message]
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
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='CAFEAcA8Hg4BrP=CqQLCmyu8ysEADqUoSuhA0_WVM9ch2tb3aHw@mail.gmail.com' \
--to=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).