From: Paul Zimmermann <Paul.Zimmermann@inria.fr>
To: Joseph Myers <joseph@codesourcery.com>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH] add inputs to auto-libm-test-in yielding larger errors
Date: Mon, 30 Nov 2020 11:34:57 +0100 [thread overview]
Message-ID: <mw5z5nrv3i.fsf@tomate.loria.fr> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2011271910480.600731@digraph.polyomino.org.uk> (message from Joseph Myers on Fri, 27 Nov 2020 19:13:04 +0000)
Dear Joseph,
submitted as https://sourceware.org/bugzilla/show_bug.cgi?id=26982, and a
similar one for tgamma (https://sourceware.org/bugzilla/show_bug.cgi?id=26983).
Paul
> Date: Fri, 27 Nov 2020 19:13:04 +0000
> From: Joseph Myers <joseph@codesourcery.com>
> CC: <libc-alpha@sourceware.org>
> User-Agent: Alpine 2.22 (DEB 394 2020-01-19)
>
> On Thu, 26 Nov 2020, Paul Zimmermann wrote:
>
> > thank you Joseph, I will commit that patch.
> >
> > I also found a case where lgamma() yields more than 10 ulps of error:
> >
> > Checking lgamma
> > x=-0x1.f60c969a239f2p+1 d=1.0410549778851831e+01
> >
> > This should be considered as a bug and entered into bugzilla?
>
> Any case where a libm function produces errors exceeding the maximum
> accepted in ulps files (9 ulps for most formats, 16 for IBM long double),
> in any rounding mode, measured in the way the libm testsuite does
> (comparing against a correctly rounded result for that rounding mode, not
> against an infinite-precision result) should be reported as a bug to
> Bugzilla if there isn't already a bug open for inaccuracy of that
> function.
>
> --
> Joseph S. Myers
> joseph@codesourcery.com
next prev parent reply other threads:[~2020-11-30 10:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-25 18:10 Paul Zimmermann
2020-11-25 22:05 ` Joseph Myers
2020-11-26 8:16 ` Paul Zimmermann
2020-11-27 19:13 ` Joseph Myers
2020-11-30 10:34 ` Paul Zimmermann [this message]
2020-11-30 22:21 ` Joseph Myers
2020-12-01 10:29 ` Paul Zimmermann
2020-12-01 22:48 ` Joseph Myers
2020-12-02 6:42 ` Paul Zimmermann
2020-12-21 5:09 ` Siddhesh Poyarekar
2020-12-09 10:05 Paul Zimmermann
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=mw5z5nrv3i.fsf@tomate.loria.fr \
--to=paul.zimmermann@inria.fr \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@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).