public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mtk dot manpages at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug math/6807] New: y0(), y1(), yn() do not raise exception and give wrong errno for pole error
Date: Thu, 31 Jul 2008 12:21:00 -0000	[thread overview]
Message-ID: <20080731122004.6807.mtk.manpages@gmail.com> (raw)

The POSIX.1 spec of y0(), y1(), yn() says:

==
Pole Error
    The value of x is zero.

    If the integer expression (math_errhandling & MATH_ERRNO) is non-zero, then
errno shall be set to [ERANGE]. If the integer expression (math_errhandling &
MATH_ERREXCEPT) is non-zero, then the divide-by-zero floating-point exception
shall be raised.
==

For a pole error, GNU's y0(), y1(), yn() set errno to EDOM, and do not raise an
IEEE exception.  This is wrong on both counts.  errno should be set to ERANGE,
and an FE_DIVBYZERO exception should occur.

Note: the POLE ERROR text was only added to POSIX.1-2001 for TC2 (i.e.,
POSIX.1-2004; before that, this case was specified as a RANGE ERROR (which is
mathematically incorrect).

Background: 
On error, many glibc math functions both set errno and raise an exception
(fetestexcept(3)).  For example, the following  function all do this: acos(),
asin(), cosh(), sinh(), acosh(), asinh(), exp(), exp2(), ldexp(), log(),
log10(), log2().  However, there is much inconsistency.  Some functions raise an
exception, but don't set errno.  Some functions set errno for some errors, but
not others.  A few set errno, but don't raise an exception.  This series of bug
reports documents deviations from what I consider the ideal: all functions
should BOTH set errno AND raise an exception for all errors.

All of these reports relate to tests on glibc 2.8 (as provided by SUSE 11.0).

-- 
           Summary: y0(), y1(), yn() do not raise exception and give wrong
                    errno for pole error
           Product: glibc
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: math
        AssignedTo: aj at suse dot de
        ReportedBy: mtk dot manpages at gmail dot com
                CC: glibc-bugs at sources dot redhat dot com


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

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


             reply	other threads:[~2008-07-31 12:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-31 12:21 mtk dot manpages at gmail dot com [this message]
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=20080731122004.6807.mtk.manpages@gmail.com \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sources.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 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).