From: Joseph Myers <joseph@codesourcery.com>
To: Steve Ellcey <sellcey@cavium.com>
Cc: "Zack Weinberg" <zackw@panix.com>,
"Ondřej Bílka" <neleai@seznam.cz>,
"Siddhesh Poyarekar" <siddhesh@gotplt.org>,
"Wilco Dijkstra" <Wilco.Dijkstra@arm.com>,
"libc-alpha@sourceware.org" <libc-alpha@sourceware.org>,
nd <nd@arm.com>
Subject: Re: [PATCH 2/6] Remove slow paths from sin/cos
Date: Sat, 10 Mar 2018 00:52:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1803100049290.28686@digraph.polyomino.org.uk> (raw)
In-Reply-To: <1520636722.6774.157.camel@cavium.com>
[-- Attachment #1: Type: text/plain, Size: 615 bytes --]
On Fri, 9 Mar 2018, Steve Ellcey wrote:
> And yet we have tests for large numbers in auto-libm-test-out-sin
> and auto-libm-test-out-cos. Â I was testing a different vector sin/cos
Yes. A floating-point number represents a particular real number, not an
interval, so all the usual accuracy goals (of results within a few ulps of
the correct answer) apply for large inputs (but performance is not a
concern for those inputs). Only for IBM long double is this relaxed, to
treat values not representable in 106 mantissa bits as if they do
represent intervals.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2018-03-10 0:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-09 15:46 Wilco Dijkstra
2018-03-09 16:17 ` Siddhesh Poyarekar
2018-03-09 18:19 ` Ondřej Bílka
2018-03-09 18:52 ` Zack Weinberg
2018-03-09 23:05 ` Steve Ellcey
2018-03-10 0:52 ` Joseph Myers [this message]
2018-03-12 15:36 ` Wilco Dijkstra
2018-03-12 15:46 ` Zack Weinberg
2018-03-12 16:10 ` Joseph Myers
2018-03-12 21:13 ` Wilco Dijkstra
2018-03-09 19:06 ` Wilco Dijkstra
2018-03-09 19:31 ` Siddhesh Poyarekar
2018-03-12 18:09 ` Wilco Dijkstra
2018-03-13 8:53 ` Siddhesh Poyarekar
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.1803100049290.28686@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=Wilco.Dijkstra@arm.com \
--cc=libc-alpha@sourceware.org \
--cc=nd@arm.com \
--cc=neleai@seznam.cz \
--cc=sellcey@cavium.com \
--cc=siddhesh@gotplt.org \
--cc=zackw@panix.com \
/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).