From: Patrick McGehearty <patrick.mcgehearty@oracle.com>
To: libc-alpha@sourceware.org
Subject: Re: [PATCH] Improves __ieee754_exp() performance by greater than 5x on sparc/x86.
Date: Fri, 20 Oct 2017 14:58:00 -0000 [thread overview]
Message-ID: <4f0a974d-4a29-71df-9a70-43413c6027e5@oracle.com> (raw)
In-Reply-To: <DB6PR0801MB2053BE30521809892DFF912483430@DB6PR0801MB2053.eurprd08.prod.outlook.com>
On 10/20/2017 8:38 AM, Wilco Dijkstra wrote:
> Patrick wrote:
>
> + fe_val = __fegetround();
>
>> Failing to use __fegetround(),__fesetround() causes over 40 math test
>> accuracy failures for other rounding modes in exp, cexp, cpow, cosh,
>> ccos, ccosh, csin, and csinh. If the glibc/Linux community were to
>> declare that the only rounding mode that was fully supported was
>> FE_TONEAREST, we could simplify/speed up a lot of code. :-)
> "Failure" is too unspecific. What is the difference in ULP? If it is from
> say 2 to 20 then yes that's an issue. If it is from 2 to 3 in a non-nearest
> rounding mode then that's perfectly acceptable.
>
> Anyway, never use __fegetround/__fesetround. Use get_rounding_mode
> which is inlined on all targets and libc_fesetround which is inlined on most
> targets.
>
> Wilco
>
>
The ULP diffs were mostly in the 2 to 3 range for the complex functions.
There no gross errors.
I appreciate the pointer to get_rounding_mode and libc_fesetround.
I was not previously aware of those functions.
I will give those a try today.
- patrick
next prev parent reply other threads:[~2017-10-20 14:58 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-20 13:38 Wilco Dijkstra
2017-10-20 14:58 ` Patrick McGehearty [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-12-29 23:42 Patrick McGehearty
2018-01-01 1:36 ` Joseph Myers
2018-01-01 16:31 ` Patrick McGehearty
2018-01-01 16:41 ` Joseph Myers
2017-12-08 23:08 Patrick McGehearty
2017-12-11 8:14 ` Siddhesh Poyarekar
2017-12-11 17:04 ` Patrick McGehearty
2017-12-11 17:53 ` Siddhesh Poyarekar
2017-12-14 1:28 ` Joseph Myers
2017-12-18 20:11 ` Patrick McGehearty
2017-12-04 21:53 Patrick McGehearty
2017-12-05 23:20 ` Joseph Myers
2017-12-01 0:51 Patrick McGehearty
2017-12-01 0:56 ` Joseph Myers
2017-11-07 4:25 Patrick McGehearty
2017-11-16 17:52 ` Patrick McGehearty
2017-11-16 18:27 ` Carlos O'Donell
2017-11-16 18:31 ` Joseph Myers
2017-11-23 21:19 ` Joseph Myers
2017-12-01 0:47 ` Patrick McGehearty
2017-10-26 22:53 Patrick McGehearty
2017-11-01 0:26 ` Joseph Myers
2017-10-26 16:44 Patrick McGehearty
2017-10-26 17:20 ` Joseph Myers
2017-10-26 17:25 ` Joseph Myers
2017-10-26 18:30 ` Patrick McGehearty
2017-10-26 19:44 ` Joseph Myers
2017-10-16 16:56 Patrick McGehearty
2017-10-18 17:22 ` Joseph Myers
2017-10-18 23:22 ` Joseph Myers
2017-10-19 22:31 ` Patrick McGehearty
2017-10-19 22:48 ` Joseph Myers
2017-10-20 15:04 ` Patrick McGehearty
2017-10-21 5:23 ` Patrick McGehearty
2017-10-23 12:47 ` Joseph Myers
2017-10-23 19:58 ` Patrick McGehearty
2017-10-23 21:31 ` Joseph Myers
2017-10-20 11:41 ` Szabolcs Nagy
2017-10-20 14:56 ` Patrick McGehearty
2017-10-20 16:10 ` Joseph Myers
2017-10-23 12:25 ` Siddhesh Poyarekar
2017-10-23 15:58 ` 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=4f0a974d-4a29-71df-9a70-43413c6027e5@oracle.com \
--to=patrick.mcgehearty@oracle.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).