public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: "Manuel López-Ibáñez" <lopezibanez@gmail.com>, linux-man@vger.kernel.org
Cc: mtk.manpages@gmail.com, GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [patch] pow.3: Add note on performance characteristics of pow
Date: Fri, 17 Oct 2014 05:24:00 -0000	[thread overview]
Message-ID: <5440A816.8000002@gmail.com> (raw)
In-Reply-To: <CAESRpQDx5TfgfRp1q69NiuCB5ve8+fR1NC2up9h5LOkogMKkqQ@mail.gmail.com>

Hello Manuel,


On 10/17/2014 01:51 AM, Manuel López-Ibáñez wrote:
> Hello,
> 
> This patch documents
> https://sourceware.org/bugzilla/show_bug.cgi?id=13932 as requested in
> https://sourceware.org/bugzilla/show_bug.cgi?id=15267. It would be
> nice to add more details, but it seems the behavior and its
> consequences is not well understood. The purpose of the note is to
> warn users of this behavior and thus avoid frustration
> (http://entropymine.com/imageworsener/slowpow/).
> 
> This is my first patch. I followed (hopefully correctly) the instructions here:
> https://www.kernel.org/doc/man-pages/patches.html


Thanks for this patch. It looks good. But inline patches are easier to review.
One small question below.

> diff --git a/man3/pow.3 b/man3/pow.3
> index d0a2ea8..3d2151a 100644
> --- a/man3/pow.3
> +++ b/man3/pow.3
> @@ -320,6 +320,17 @@ 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 inputs than for other nearby

I plan to change "some" to "some (rare)". Sound okay? The point is not to
worry people that this is a problem that is commonly encountered. (Or is it?)

Thanks,

Michael

> +inputs. The inputs that produce such behavior are different for
> +.BR powf (),
> +.BR pow ()
> +and
> +.BR powl ().
> +
>  In glibc 2.9 and earlier,
>  .\"
>  .\" http://sources.redhat.com/bugzilla/show_bug.cgi?id=6776


-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/

  reply	other threads:[~2014-10-17  5:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-16 23:52 Manuel López-Ibáñez
2014-10-17  5:24 ` Michael Kerrisk (man-pages) [this message]
2014-10-17  7:58   ` Siddhesh Poyarekar
2014-10-17 13:51     ` Manuel López-Ibáñez
2014-10-30 23:30       ` Manuel López-Ibáñez
2014-11-11 12:58       ` Michael Kerrisk (man-pages)

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=5440A816.8000002@gmail.com \
    --to=mtk.manpages@gmail.com \
    --cc=libc-alpha@sourceware.org \
    --cc=linux-man@vger.kernel.org \
    --cc=lopezibanez@gmail.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).