public inbox for newlib@sourceware.org
 help / color / mirror / Atom feed
From: "Keith Packard" <keithp@keithp.com>
To: Paul Zimmermann <Paul.Zimmermann@inria.fr>
Cc: newlib@sourceware.org
Subject: Re: issue with tgammaf
Date: Thu, 17 Sep 2020 09:11:51 -0700	[thread overview]
Message-ID: <878sd8e62g.fsf@keithp.com> (raw)
In-Reply-To: <mwmu1odg6u.fsf@tomate.loria.fr>

[-- Attachment #1: Type: text/plain, Size: 1034 bytes --]

Paul Zimmermann <Paul.Zimmermann@inria.fr> writes:

>> You might have more luck with lgammaf_r as that avoids use of
>> _impure_ptr in newlib.
>
> thank you very much Keith, that made it. The results for lgammaf_r are
> the same as those with OpenLibm and Musl:

That isn't surprising; so many libraries math support can be traced back
to the original SunPro code.

Thanks much for doing this analysis; it's nice to see careful
measurements of how accurate each of these C libraries is. Have you
published the test framework so we can replicate these results and
monitor their change over time?

Do you know that newlib has two different sets of 32-bit math functions?
Arm supplied a new set of many common math functions that use 64-bit
doubles for the intermediate computations? I'd be very interested in
measuring the effect of that code on accuracy. The new paths are
selected by compiling newlib with -D__OBSOLETE_MATH_DEFAULT=0 while the
old can be selected with -D__OBSOLETE_MATH_DEFAULT=1

-- 
-keith

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2020-09-17 16:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-15  8:21 Paul Zimmermann
2020-09-15 17:28 ` Keith Packard
2020-09-16  8:33   ` Paul Zimmermann
2020-09-16 15:13     ` Keith Packard
2020-09-17  7:18       ` Paul Zimmermann
2020-09-17 16:11         ` Keith Packard [this message]
2021-01-13  5:46           ` Paul Zimmermann
2021-01-13  6:38             ` Keith Packard
2021-01-13  7:52               ` Paul Zimmermann
2020-09-18 21:21   ` Jeff Johnston

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=878sd8e62g.fsf@keithp.com \
    --to=keithp@keithp.com \
    --cc=Paul.Zimmermann@inria.fr \
    --cc=newlib@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).