public inbox for newlib@sourceware.org
 help / color / mirror / Atom feed
From: Paul Zimmermann <Paul.Zimmermann@inria.fr>
To: joel@rtems.org
Cc: keithp@keithp.com, newlib@sourceware.org,
	christoph.lauter@christoph-lauter.org,
	Jean-Michel.Muller@ens-lyon.fr, sibid@uvic.ca
Subject: Re: correctly rounded mathematical functions
Date: Thu, 06 Jan 2022 11:12:02 +0100	[thread overview]
Message-ID: <mwleztyxzh.fsf@tomate.loria.fr> (raw)
In-Reply-To: <CAF9ehCWJMRSdHQqo6joqyjYr6NAYZMOVS5eYgCEfrm6Rz680Qg@mail.gmail.com> (message from Joel Sherrill on Wed, 5 Jan 2022 13:00:35 -0600)

       Dear Joel,

> I hate to ask since I know this is unrelated but what is the best source for
> properly licensed and accurate long double methods. I am still hoping that
> part of an RTEMS GSoC project is to merge them from somewhere into
> newlib.

as far as I know, four libraries provide long double functions:
GNU libc, Intel Math Library, OpenLibm and Musl. See Table 11 from
https://members.loria.fr/PZimmermann/papers/accuracy.pdf.

And of course we also plan to provide (correctly rounded) long double
functions, acos and cbrt are already available on the CORE-MATH page.

> And I'm thrilled at all the autoconf/automake work. That has really
> been a challenge
> for students.

Best regards,
Paul

  reply	other threads:[~2022-01-06 10:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-03 12:57 Paul Zimmermann
2022-01-03 20:41 ` Joel Sherrill
2022-01-04  9:44   ` Paul Zimmermann
2022-01-04 15:23     ` Joel Sherrill
2022-01-04 15:44       ` Paul Zimmermann
2022-01-04 18:01       ` Jeff Johnston
2022-01-05 10:33         ` Paul Zimmermann
2022-01-04 18:50       ` Keith Packard
2022-01-05 11:39         ` Paul Zimmermann
2022-01-05 19:00           ` Joel Sherrill
2022-01-06 10:12             ` Paul Zimmermann [this message]
2022-01-06 14:51               ` Joel Sherrill
2022-01-06 15:33                 ` Paul Zimmermann
2022-01-05 19:43           ` Keith Packard

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=mwleztyxzh.fsf@tomate.loria.fr \
    --to=paul.zimmermann@inria.fr \
    --cc=Jean-Michel.Muller@ens-lyon.fr \
    --cc=christoph.lauter@christoph-lauter.org \
    --cc=joel@rtems.org \
    --cc=keithp@keithp.com \
    --cc=newlib@sourceware.org \
    --cc=sibid@uvic.ca \
    /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).