From: Joseph Myers <joseph@codesourcery.com>
To: Joel Sherrill <joel.sherrill@oarcorp.com>
Cc: Dionna Amalie Glaze <dionnaglaze@google.com>,
Aditya Upadhyay <aadit0402@gmail.com>,
"newlib@sourceware.org" <newlib@sourceware.org>
Subject: Re: Long double complex methods
Date: Thu, 29 Jun 2017 16:18:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1706291614050.7727@digraph.polyomino.org.uk> (raw)
In-Reply-To: <f8e36f0e-ab65-6aa0-2d0c-0750de7ec57c@oarcorp.com>
On Wed, 28 Jun 2017, Joel Sherrill wrote:
> Also, although I don't know how to run them, doesn't someone
> run glibc tests on newlib? They likely have tests for this for
> newlib's purposes.
It would be interesting to see results of glibc libm tests (current git
please, there have been major changes since the last release) for a range
of libm implementations and operating systems, but also probably a lot of
work to get them building with other C libraries; they make plenty of use
of glibc features, include some internal glibc headers for configuration
of some details of the architecture, and hardcode glibc choices of goals
for errno, exceptions and accuracy that other libm implementations may
differ on. An implementation/architecture-specific libm-test-ulps file
also needs to be generated before you can expect clean results even for an
implementation following glibc's goals.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2017-06-29 16:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-28 20:35 Aditya Upadhyay
2017-06-28 21:36 ` Dionna Amalie Glaze via newlib
2017-06-28 21:57 ` Joel Sherrill
2017-06-29 16:18 ` Joseph Myers [this message]
2017-06-29 16:31 ` Joel Sherrill
2017-06-29 6:39 ` Corinna Vinschen
2017-06-29 7:11 ` Aditya Upadhyay
2017-06-29 11:53 ` Corinna Vinschen
2017-06-29 12:04 ` Corinna Vinschen
2017-06-29 19:38 ` Yaakov Selkowitz
2017-06-29 21:17 ` Joel Sherrill
2017-06-30 9:11 ` Aditya Upadhyay
2017-07-04 21:31 ` Aditya Upadhyay
2017-07-04 21:56 ` Aditya Upadhyay
2017-07-05 8:27 ` Corinna Vinschen
2017-07-05 9:02 ` Aditya Upadhyay
2017-07-05 12:40 ` Corinna Vinschen
2022-11-08 18:31 ` [newlib] Generally make all 'long double complex' methods available in <complex.h> Thomas Schwinge
2022-11-08 20:24 ` Jeff Johnston
2017-06-29 13:47 ` Long double complex methods Joel Sherrill
-- strict thread matches above, loose matches on Subject: below --
2017-06-28 13:53 Aditya Upadhyay
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.DEB.2.20.1706291614050.7727@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=aadit0402@gmail.com \
--cc=dionnaglaze@google.com \
--cc=joel.sherrill@oarcorp.com \
--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).