qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: G 3 <programmingkidx@gmail.com>
To: Peter Maydell <peter.maydell@linaro.org>
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 10:33:46 -0400	[thread overview]
Message-ID: <F705365A-5746-44BA-B820-33A4A993EDDD@gmail.com> (raw)
In-Reply-To: <CAFEAcA9zU9w6_UeU4qb9Y4q52vR3TtBDSfvWWTUXQuSaCjGEFA@mail.gmail.com>


On Sep 27, 2016, at 7:43 AM, Peter Maydell wrote:

> On 26 September 2016 at 18:05, G 3 <programmingkidx@gmail.com> wrote:
>> I made my own experimental implementation of the fmadds  
>> instruction that I
>> would like to add to QEMU. How would I do this?
>>
>> My implementation would probably look like this:
>>
>> void fmadds(float *frD, float frA, float frC, float frB)
>> {
>>         *frD = frA * frC + frB;
>> }
>
> This isn't portable, because different host CPUs can have
> different implementations of floating point arithmetic
> with subtle differences (notably in corner cases like
> subnormals and also related to the floating point exception
> flags). This is why we use the softfloat library in fpu/,
> which (although slow) is guaranteed to give the right results.
> We did use to have a version of the fpu functions which
> used a "just do a C float or double operation", but we
> removed it many years ago for this reason.
>
> 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.

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?

  reply	other threads:[~2016-09-27 14:34 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 [this message]
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

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=F705365A-5746-44BA-B820-33A4A993EDDD@gmail.com \
    --to=programmingkidx@gmail.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).