public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Szabolcs Nagy <szabolcs.nagy@arm.com>
To: Patrick McGehearty <patrick.mcgehearty@oracle.com>,
	libc-alpha@sourceware.org
Cc: nd@arm.com
Subject: Re: [PATCH v2] Improves __ieee754_exp(x) performance by 18-37% when |x| < 1.0397
Date: Thu, 19 Apr 2018 09:14:00 -0000	[thread overview]
Message-ID: <fd75ba40-5d50-74ee-c640-dc9d6ae44ff8@arm.com> (raw)
In-Reply-To: <1523048295-90391-1-git-send-email-patrick.mcgehearty@oracle.com>

On 06/04/18 21:58, Patrick McGehearty wrote:
> Adds a fast path to e_exp.c when |x| < 1.03972053527832.
> When values are tested in isolation, reduction in execution
> time is: aarch 30%, sparc 18%, x86 37%.
> When comparing benchtests/bench.out which includes values
> outside that range, the gains are:
> aarch 8%, sparc 5%, x86 9%.
> 
> make check is clean (no increase in ulp for any math test).
> Testing 20M values for each rounding mode in that range shows
> approximately one in 200 values is off by 1 ulp. No value tested
> for exp(x) changed by 2 or more ulp.
> 
> No observed change in performance or accuracy for x outside
> fast path range.
> 
> These changes will be active for all platforms that don't provide
> their own exp() routines. They will also be active for ieee754
> versions of ccos, ccosh, cosh, csin, csinh, sinh, exp10, gamma, and
> erf.
> 
> New in this version:
> Copyright year for eexp.tbl changed from 2017 to 2018.
> Spurious white space diff e_exp.c removed.
> 
> ChangeLog:
> 2018-03-20  Patrick McGehearty <patrick.mcgehearty@oracle.com>
> 
>          * sysdeps/ieee754/dbl-64/e_exp.c: faster __ieee754_exp()
>          * sysdeps/ieee754/dbl-64/eexp.tbl: New file for e_exp.c

looks ok to me.

Reviewed-by: Szabolcs Nagy <szabolcs.nagy@arm.com>

      reply	other threads:[~2018-04-19  9:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-06 20:58 Patrick McGehearty
2018-04-19  9:14 ` Szabolcs Nagy [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=fd75ba40-5d50-74ee-c640-dc9d6ae44ff8@arm.com \
    --to=szabolcs.nagy@arm.com \
    --cc=libc-alpha@sourceware.org \
    --cc=nd@arm.com \
    --cc=patrick.mcgehearty@oracle.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).