From: Damian McGuckin <damianm@esi.com.au>
To: Szabolcs Nagy <nsz@port70.net>
Cc: musl@lists.openwall.com
Subject: Re: Possible Mistype in exp.c
Date: Wed, 30 Jan 2019 22:14:01 +1100 (AEDT) [thread overview]
Message-ID: <alpine.LRH.2.02.1901302041090.22755@key0.esi.com.au> (raw)
In-Reply-To: <20190130093738.GE21289@port70.net>
On Wed, 30 Jan 2019, Szabolcs Nagy wrote:
> i work at arm and i did this work there so i know the background.
That explains everything.
> there is not much published about the algorithms (although there aren't
> many new ideas in the code,
Sadly, a lot of the existing ideas are not documented well. Even the texts
on this topic seem to be lacking all the information to actually implement
a fast low-level routine. They cover fundamentals well and important
topics like error analysis but omit the basic techniques and little
details and basic techniques that are needed to make it fast and still
achieve that 1*ULP (or better) error bound.
> it's mostly about optimizing for modern cpus), but i plan to at least
> put the polynomial and lookup table generation code in that repo.
Thanks. For some reason, I have this aversion to table lookup because
suddenly there are lots more numbers hanging about. But, it certainly
helps to achieve optimal performance. I had a look at the GLIBC exp.c
which comes out of the Ultimate Libray done by IBM and I find that
inpossible to read/comprehend especially with its table lookups.
> the polynomial coefficients were generated with the sollya tool from
> inria.
Yes, nice tool. What range reduction is used for those routines and why
are there several polynomials? Just curious.
Regards - Damian
Pacific Engineering Systems International, 277-279 Broadway, Glebe NSW 2037
Ph:+61-2-8571-0847 .. Fx:+61-2-9692-9623 | unsolicited email not wanted here
Views & opinions here are mine and not those of any past or present employer
next prev parent reply other threads:[~2019-01-30 11:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-28 6:59 Damian McGuckin
2019-01-29 11:01 ` Szabolcs Nagy
2019-01-29 11:26 ` Damian McGuckin
2019-01-29 11:43 ` Szabolcs Nagy
2019-01-30 1:18 ` Damian McGuckin
2019-01-30 9:37 ` Szabolcs Nagy
2019-01-30 11:14 ` Damian McGuckin [this message]
2019-01-30 12:19 ` Szabolcs Nagy
2019-01-30 12:44 ` Alexander Monakov
2019-01-30 14:10 ` Szabolcs Nagy
2019-02-01 23:26 ` Morten Welinder
2019-02-02 3:39 ` Szabolcs Nagy
2019-02-03 2:05 ` Morten Welinder
2019-02-03 3:07 ` Damian McGuckin
2019-04-03 1:13 ` Floating Point Accuracy Damian McGuckin
2019-01-30 12:56 ` Possible Mistype in exp.c Damian McGuckin
2019-01-31 0:04 ` Szabolcs Nagy
2019-01-31 0:39 ` Damian McGuckin
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=alpine.LRH.2.02.1901302041090.22755@key0.esi.com.au \
--to=damianm@esi.com.au \
--cc=musl@lists.openwall.com \
--cc=nsz@port70.net \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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).