public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <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: Wed, 04 Dec 2013 14:40:00 -0000	[thread overview]
Message-ID: <bug-6807-131-WCf5nn4j44@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-6807-131@http.sourceware.org/bugzilla/>

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

--- Comment #6 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GNU C Library master sources".

The branch, master has been updated
       via  699ff83712b5796ac50ed332d9dad55d38450e81 (commit)
      from  5b118558f9fb0620508d51c34c2cb5ba4f1f01c2 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=699ff83712b5796ac50ed332d9dad55d38450e81

commit 699ff83712b5796ac50ed332d9dad55d38450e81
Author: Joseph Myers <joseph@codesourcery.com>
Date:   Wed Dec 4 14:39:37 2013 +0000

    Fix Bessel function error handling (bug 6807, bug 15901).

-----------------------------------------------------------------------

Summary of changes:
 ChangeLog                           |   28 +++++++++++++++
 NEWS                                |   24 ++++++------
 math/libm-test.inc                  |   66 +++++++++++++++++++++++++++++------
 math/w_j0.c                         |    7 +++-
 math/w_j0f.c                        |    7 +++-
 math/w_j0l.c                        |    7 +++-
 math/w_j1.c                         |    7 +++-
 math/w_j1f.c                        |    7 +++-
 math/w_j1l.c                        |    7 +++-
 math/w_jn.c                         |    7 +++-
 math/w_jnf.c                        |    7 +++-
 sysdeps/i386/fpu/libm-test-ulps     |    3 ++
 sysdeps/ieee754/k_standard.c        |   16 +++++----
 sysdeps/ieee754/ldbl-128/e_jnl.c    |    2 +-
 sysdeps/ieee754/ldbl-128ibm/e_jnl.c |    2 +-
 sysdeps/ieee754/ldbl-96/e_jnl.c     |    3 +-
 sysdeps/x86_64/fpu/libm-test-ulps   |    5 +++
 17 files changed, 156 insertions(+), 49 deletions(-)

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


  parent reply	other threads:[~2013-12-04 14:40 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 [this message]
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
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-WCf5nn4j44@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).