From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: "Manuel López-Ibáñez" <lopezibanez@gmail.com>,
"Siddhesh Poyarekar" <siddhesh@redhat.com>
Cc: mtk.manpages@gmail.com, linux-man@vger.kernel.org,
GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [patch] pow.3: Add note on performance characteristics of pow
Date: Tue, 11 Nov 2014 13:58:33 +0100 [thread overview]
Message-ID: <546207F9.9050308@gmail.com> (raw)
In-Reply-To: <CAESRpQB5K9U1sBreXUrNa4tPB69cwxC+fdu1bUr5BkU-dtxJMQ@mail.gmail.com>
Hello Manuel,
On 10/17/2014 03:51 PM, Manuel López-Ibáñez wrote:
> On 17 October 2014 09:58, Siddhesh Poyarekar <siddhesh@redhat.com> wrote:
>>>> +inputs. The inputs that produce such behavior are different for
>>>> +.BR powf (),
>>>> +.BR pow ()
>>>> +and
>>>> +.BR powl ().
>>>> +
>>
>> The slow fallback is only taken for pow, not powf or powl.
>
> Updated patch inline:
>
> diff --git a/man3/pow.3 b/man3/pow.3
> index d0a2ea8..1b05292 100644
> --- a/man3/pow.3
> +++ b/man3/pow.3
> @@ -320,6 +320,18 @@ The variant returning
> also conforms to
> SVr4, 4.3BSD, C89.
> .SH BUGS
> +On 64-bits,
> +.\"
> +.\" https://sourceware.org/bugzilla/show_bug.cgi?id=13932
> +.BR pow ()
> +may be more than 10,000 times slower for some (rare) inputs than for
> other nearby
> +inputs. This only affects
> +.BR pow (),
> +and not
> +.BR powf ()
> +nor
> +.BR powl ().
> +
> In glibc 2.9 and earlier,
> .\"
> .\" http://sources.redhat.com/bugzilla/show_bug.cgi?id=6776
>
> and attached in case gmail messes it up.
Thanks for revising the patch. I've applied it.
Cheers,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
prev parent reply other threads:[~2014-11-11 12:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-16 23:51 [patch] pow.3: Add note on performance characteristics of pow Manuel López-Ibáñez
[not found] ` <CAESRpQDx5TfgfRp1q69NiuCB5ve8+fR1NC2up9h5LOkogMKkqQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-10-17 5:24 ` Michael Kerrisk (man-pages)
[not found] ` <5440A816.8000002-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-10-17 7:58 ` Siddhesh Poyarekar
[not found] ` <20141017075845.GL1552-EBXREzpM9Zo4v7BKUif6HKfLeoKvNuZc@public.gmane.org>
2014-10-17 13:51 ` Manuel López-Ibáñez
[not found] ` <CAESRpQB5K9U1sBreXUrNa4tPB69cwxC+fdu1bUr5BkU-dtxJMQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-10-30 23:30 ` Manuel López-Ibáñez
2014-11-11 12:58 ` Michael Kerrisk (man-pages) [this message]
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=546207F9.9050308@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-man@vger.kernel.org \
--cc=lopezibanez@gmail.com \
--cc=siddhesh@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.