From: Joel Sherrill <joel@rtems.org>
To: Paul Zimmermann <Paul.Zimmermann@inria.fr>
Cc: Newlib <newlib@sourceware.org>
Subject: Re: OpenLibm?
Date: Thu, 2 Dec 2021 08:30:30 -0600 [thread overview]
Message-ID: <CAF9ehCW1Lbtehyzo4Zk02Zn7cLsftimSN9Cua=kYVyNaEM8nNg@mail.gmail.com> (raw)
In-Reply-To: <mwsfvb1ljj.fsf@tomate.loria.fr>
On Thu, Dec 2, 2021 at 2:03 AM Paul Zimmermann <Paul.Zimmermann@inria.fr> wrote:
>
> about Joel's mail (https://sourceware.org/pipermail/newlib/2021/018739.html).
>
> OpenLibm long double does not implement exp10, j0, j1, y0 and y1, and has
> accuracy issues with lgamma and tgamma. See Table 11 of
> https://members.loria.fr/PZimmermann/papers/#accuracy.
OK both have issues. I'd like long double support in newlib's libm to
improve standards compliance. I was looking for an implementation.
Issue: newlib has no long double support when sizeof(long double) !=
sizeof(double).
Random thoughts:
+ For the missing openlibm methods, newlib's implementation of those
methods could be submitted to openlibm.
+ Does newlib have an accuracy document?
+ Is newlib's accuracy better than openlibm's?
+ Would it make sense to port long double methods from openlibm to newlib?
I'm just trying to find a technical path to get long double into newlib.
I have no vested interest in any particular path that achieves that.
If we can agree on a technical path, RTEMS could add this as a potential
Google Summer of Code 2022 project.
--joel
> Paul
next prev parent reply other threads:[~2021-12-02 14:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-02 8:02 OpenLibm? Paul Zimmermann
2021-12-02 14:30 ` Joel Sherrill [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-12-01 23:32 OpenLibm? Joel Sherrill
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='CAF9ehCW1Lbtehyzo4Zk02Zn7cLsftimSN9Cua=kYVyNaEM8nNg@mail.gmail.com' \
--to=joel@rtems.org \
--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).