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/6807] y0(), y1(), yn() do not raise exception and give wrong errno for pole error
Date: Tue, 26 May 2020 10:26:01 +0000	[thread overview]
Message-ID: <bug-6807-131-BpiRSqx9Uq@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-6807-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=6807

--- Comment #9 from Michael Kerrisk <mtk.manpages at gmail dot com> ---
y0(3) manual page has been patched to note the fix.

diff --git a/man3/y0.3 b/man3/y0.3
index 07e20bd78..460a63ad9 100644
--- a/man3/y0.3
+++ b/man3/y0.3
@@ -187,15 +187,11 @@ Pole error: \fIx\fP is 0.0
 .\" as a range error.
 .I errno
 is set to
-.\" FIXME . y0(0.0) gives EDOM
 .BR ERANGE
-(but see BUGS).
-No
+and an
 .B FE_DIVBYZERO
-exception is returned by
-.BR fetestexcept (3)
-for this case.
-.\" Bug raised: http://sources.redhat.com/bugzilla/show_bug.cgi?id=6808
+exception is raised
+(but see BUGS).
 .TP
 Range error: result underflow
 .\" e.g., y0(1e33) on glibc 2.8/x86-32
@@ -253,15 +249,18 @@ conform to SVr4, 4.3BSD,
 POSIX.1-2001, POSIX.1-2008.
 The others are nonstandard functions that also exist on the BSDs.
 .SH BUGS
-On a pole error, these functions set
+Before glibc 2.19,
+.\" http://sourceware.org/bugzilla/show_bug.cgi?id=6807
+these functions misdiagnosed pole errors:
 .I errno
-to
+was set to
 .BR EDOM ,
 instead of
 .BR ERANGE
+and no
+.B FE_DIVBYZERO
+exception was raised.
 as POSIX.1-2004 requires.
-.\" FIXME .
-.\" Bug raised: http://sourceware.org/bugzilla/show_bug.cgi?id=6807
 .PP
 In glibc version 2.3.2 and earlier,
 .\" FIXME . Actually, 2.3.2 is the earliest test result I have; so yet

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2020-05-26 10:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-6807-131@http.sourceware.org/bugzilla/>
2012-03-01 17:57 ` jsm28 at gcc dot gnu.org
2013-12-04 14:40 ` cvs-commit at gcc dot gnu.org
2013-12-04 14:41 ` jsm28 at gcc dot gnu.org
2014-06-13 11:16 ` fweimer at redhat dot com
2020-05-26 10:26 ` mtk.manpages at gmail dot com [this message]
2008-07-31 12:21 [Bug math/6807] New: " mtk dot manpages at gmail dot com
2008-07-31 12:23 ` [Bug math/6807] " mtk dot manpages at gmail dot com
2008-07-31 12:23 ` mtk dot manpages at gmail dot com
2008-07-31 12:25 ` mtk dot manpages at gmail dot com
2008-07-31 12:34 ` mtk dot 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-6807-131-BpiRSqx9Uq@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).