From: Joseph Myers <joseph@codesourcery.com>
To: Wilco Dijkstra <Wilco.Dijkstra@arm.com>
Cc: "libc-alpha@sourceware.org" <libc-alpha@sourceware.org>, nd <nd@arm.com>
Subject: Re: [PATCH 3/7] sin/cos slow paths: remove slow paths from small range reduction
Date: Thu, 22 Mar 2018 22:28:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1803222227560.6153@digraph.polyomino.org.uk> (raw)
In-Reply-To: <DB6PR0801MB20536EF05DE5CFE1BD1078C583AA0@DB6PR0801MB2053.eurprd08.prod.outlook.com>
On Wed, 21 Mar 2018, Wilco Dijkstra wrote:
> This patch improves the accuracy of the range reduction. When the input is
> large (2^27) and very close to a multiple of PI/2, using 110 bits of PI is not
> enough. Improve range reduction accuracy to 136 bits. As a result the special
> checks for results close to zero can be removed. The ULP of the polynomials is
> at worst 0.55ULP, so there is no reason for the slow functions, and they can be
> removed.
OK.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2018-03-22 22:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-21 17:52 Wilco Dijkstra
2018-03-22 22:28 ` Joseph Myers [this message]
2018-03-22 22:28 ` Joseph Myers
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.1803222227560.6153@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=Wilco.Dijkstra@arm.com \
--cc=libc-alpha@sourceware.org \
--cc=nd@arm.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).