public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mtk.manpages at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug math/13932] dbl-64 pow unexpectedly slow for some inputs
Date: Sat, 23 May 2020 19:32:29 +0000 [thread overview]
Message-ID: <bug-13932-131-2hg0nMkOVc@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13932-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=13932
Michael Kerrisk <mtk.manpages at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mtk.manpages at gmail dot com
--- Comment #25 from Michael Kerrisk <mtk.manpages at gmail dot com> ---
Fix documented for man-pages-5.07.
diff --git a/man3/pow.3 b/man3/pow.3
index 2f8b340bb..91b9a9562 100644
--- a/man3/pow.3
+++ b/man3/pow.3
@@ -329,9 +329,10 @@ The variant returning
also conforms to
SVr4, 4.3BSD, C89.
.SH BUGS
-On 64-bits,
+Before glibc 2.28,
.\"
.\" https://sourceware.org/bugzilla/show_bug.cgi?id=13932
+on some architectures (e.g., x86-64)
.BR pow ()
may be more than 10,000 times slower for some (rare) inputs
than for other nearby inputs.
@@ -341,6 +342,9 @@ and not
.BR powf ()
nor
.BR powl ().
+This problem was fixed
+.\" commit c3d466cba1692708a19c6ff829d0386c83a0c6e5
+in glibc 2.28.
.PP
In glibc 2.9 and earlier,
.\"
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-05-23 19:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-31 2:23 [Bug math/13932] New: x86_64 " ppluzhnikov at google dot com
2012-12-13 16:45 ` [Bug math/13932] " manu at gcc dot gnu.org
2012-12-13 18:58 ` ppluzhnikov at google dot com
2013-01-04 11:33 ` siddhesh at redhat dot com
2013-01-04 23:24 ` herve at guillemet dot org
2013-03-08 14:08 ` manu at gcc dot gnu.org
2013-03-11 6:29 ` siddhesh at redhat dot com
2013-03-11 6:36 ` siddhesh at redhat dot com
2013-03-11 9:07 ` manu at gcc dot gnu.org
2013-03-11 10:19 ` siddhesh at redhat dot com
2013-08-24 21:39 ` vz-sourceware at zeitlins dot org
2013-12-03 18:42 ` jsm28 at gcc dot gnu.org
2014-02-06 18:27 ` [Bug math/13932] dbl-64 " jsm28 at gcc dot gnu.org
2014-05-07 15:42 ` jsm28 at gcc dot gnu.org
2014-06-12 19:26 ` fweimer at redhat dot com
2020-05-23 19:32 ` mtk.manpages at gmail dot com [this message]
2020-05-23 21:31 ` vincent-srcware at vinc17 dot net
2020-05-25 11:38 ` mtk.manpages at gmail dot com
2020-05-25 12:08 ` vincent-srcware at vinc17 dot net
2020-05-25 13:19 ` mtk.manpages at gmail dot com
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=bug-13932-131-2hg0nMkOVc@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@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).