pow.3: Several bugs in glibc's pow() implementation were fixed in glibc 2.16

See https://www.sourceware.org/bugzilla/show_bug.cgi?id=3866.

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2020-05-23 22:04:46 +02:00
parent 427e4505b0
commit 831db5db46
1 changed files with 6 additions and 20 deletions

View File

@ -345,6 +345,12 @@ This problem was fixed
.\" commit c3d466cba1692708a19c6ff829d0386c83a0c6e5
in glibc 2.28.
.PP
A number of bugs
.\" http://sources.redhat.com/bugzilla/show_bug.cgi?id=3866
in the glibc implementation of
.BR pow ()
were fixed in glibc version 2.16.
.PP
In glibc 2.9 and earlier,
.\"
.\" http://sources.redhat.com/bugzilla/show_bug.cgi?id=6776
@ -359,26 +365,6 @@ Since version 2.10,
.\" and I don't have a 2.9 system to test
glibc does the right thing.
.PP
If
.I x
is negative,
then large negative or positive
.I y
values yield a NaN as the function result, with
.I errno
set to
.BR EDOM ,
and an invalid
.RB ( FE_INVALID )
floating-point exception.
For example, with
.BR pow (),
one sees this behavior when the absolute value of
.I y
is greater than about 9.223373e18.
.\" see bug http://sources.redhat.com/bugzilla/show_bug.cgi?id=3866
.\" and http://sources.redhat.com/bugzilla/show_bug.cgi?id=369
.PP
In version 2.3.2 and earlier,
.\" FIXME . Actually, 2.3.2 is the earliest test result I have; so yet
.\" to confirm if this error occurs only in 2.3.2.