From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Richard Henderson <richard.henderson@linaro.org>, qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, berrange@redhat.com
Subject: Re: [PATCH] utils: Use fma in qemu_strtosz
Date: Mon, 15 Mar 2021 10:10:37 +0100 [thread overview]
Message-ID: <0697b6d1-0a64-3d71-2f7f-3c52a005b77b@redhat.com> (raw)
In-Reply-To: <20210314234821.1954428-1-richard.henderson@linaro.org>
On 3/15/21 12:48 AM, Richard Henderson wrote:
> Use fma to simulatneously scale and round up fraction.
"simultaneously"
> The libm function will always return a properly rounded double precision
> value, which will eliminate any extra precision the x87 co-processor may
> give us, which will keep the output predictable vs other hosts.
>
> Adding DBL_EPSILON while scaling should help with fractions like
> 12.345, where the closest representable number is actually 12.3449*.
>
> Signed-off-by: Richard Henderson <richard.henderson@linaro.org>
> ---
> util/cutils.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/util/cutils.c b/util/cutils.c
> index d89a40a8c3..f7f8e48a68 100644
> --- a/util/cutils.c
> +++ b/util/cutils.c
> @@ -342,7 +342,7 @@ static int do_strtosz(const char *nptr, const char **end,
> if (val > (UINT64_MAX - ((uint64_t) (fraction * mul))) / mul) {
Shouldn't we use fma() here too? ^^^^^^^^^^^^^^^^^^^^^^^^^^
> retval = -ERANGE;
> goto out;
> }
> - *result = val * mul + (uint64_t) (fraction * mul);
> + *result = val * mul + (uint64_t)fma(fraction, mul, DBL_EPSILON);
> retval = 0;
>
> out:
>
next prev parent reply other threads:[~2021-03-15 9:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-14 23:48 [PATCH] utils: Use fma in qemu_strtosz Richard Henderson
2021-03-15 5:32 ` Thomas Huth
2021-03-15 13:20 ` Richard Henderson
2021-03-15 9:10 ` Philippe Mathieu-Daudé [this message]
2021-03-15 11:40 ` Eric Blake
2021-03-15 13:19 ` Richard Henderson
2021-03-15 11:38 ` Eric Blake
2021-03-15 13:27 ` Richard Henderson
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=0697b6d1-0a64-3d71-2f7f-3c52a005b77b@redhat.com \
--to=philmd@redhat.com \
--cc=berrange@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).