mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Damian McGuckin <damianm@esi.com.au>
To: musl@lists.openwall.com
Subject: atanhf(x) Slight Accuracy Improvements
Date: Wed, 13 Mar 2019 22:18:41 +1100 (AEDT)	[thread overview]
Message-ID: <alpine.LRH.2.02.1903132105140.4826@key0.esi.com.au> (raw)


Hi all,

Currently this routine does not achieve accuracy < ULP across all of its 
domain. For half of its domain, it worst error exceeds that limit by 
about 10%.

By tweaking some algebra, this can be made more accurate. A comparison of 
the more accurate version and the original is noted below.

 	ATANF ... FROM ... TO     WORST ERROR  % > EPS/2   MEAN ERROR
 	--------------------------------------------------------------
 	Accurate:0.00000..0.17000 1.00023*EPS   0.76907%   0.01967*EPS
 	Original:0.00000..0.17000 1.09363*EPS   0.71616%   0.01941*EPS
 	Accurate:0.17000..0.55000 0.99151*EPS   5.52206%   0.21620*EPS
 	Original:0.17000..0.55000 1.12779*EPS   8.87471%   0.23922*EPS
 	Accurate:0.55000..1.00000 0.68151*EPS   1.34789%   0.19159*EPS
 	Original:0.55000..1.00000 0.68372*EPS   1.40897%   0.19207*EPS

I see a reduction in the worst error across the entire spectrum and reduce 
slightly the percentage exceeding 0.5*ULP in most cases. The mean error is 
much the same. I have yet to rework the double version.

However, across a subset of its argument range, namely

 	[0 ..(sqrt(2)-1)/(sqrt(2)+1)]

I cannot crack the 1.0*ULP barrier if the computation of the argument
reduction

 	f = 2*(y + (y*y)/(1-y))  <---- LITTLE PROBLEM

is done in single precision. The error in the 23rd bit causes me grief.

Doing that sole calculation in double precision and then storing it as a 
float brings the worst error to 0.99*ULP. I want to avoid any extended
precision.

Note that I used the same accuracy tweak for log1p as done in log2 to 
avoid the cancellation error seen in

 	f - (f*f)/2

Any suggestions are welcome on how to get one extra bit of accuracy in my 
calculation of 'LITTLE PROBLEM' above. Using the approach as seen in 'sq() 
in 'hypotf' makes things worse unless I am doing something really wrong.

Thanks - 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


             reply	other threads:[~2019-03-13 11:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-13 11:18 Damian McGuckin [this message]
2019-03-15  1:24 ` Damian McGuckin
2019-03-17 11:41   ` Damian McGuckin
2019-03-17 23:07     ` Szabolcs Nagy
2019-03-17 23:46       ` 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.1903132105140.4826@key0.esi.com.au \
    --to=damianm@esi.com.au \
    --cc=musl@lists.openwall.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.
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).