public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jsm28 at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug math/14155] Spurious underflow exceptions from Bessel functions
Date: Thu, 24 May 2012 00:24:00 -0000	[thread overview]
Message-ID: <bug-14155-131-6Gns3mAquR@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-14155-131@http.sourceware.org/bugzilla/>

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

Joseph Myers <jsm28 at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Spurious underflow          |Spurious underflow
                   |exception from jnf          |exceptions from Bessel
                   |                            |functions

--- Comment #1 from Joseph Myers <jsm28 at gcc dot gnu.org> 2012-05-24 00:24:29 UTC ---
Spurious exceptions also arise from "double" functions:

j0 (0x1.d7ce3ap+107)
jn (2, 0x1.ffff62p+99)
y1 (0x1.27e204p+99)

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


  reply	other threads:[~2012-05-24  0:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-24  0:20 [Bug math/14155] New: Spurious underflow exception from jnf jsm28 at gcc dot gnu.org
2012-05-24  0:24 ` jsm28 at gcc dot gnu.org [this message]
2012-06-13 21:20 ` [Bug math/14155] Spurious underflow exceptions from Bessel functions jsm28 at gcc dot gnu.org
2013-03-14 17:50 ` jsm28 at gcc dot gnu.org
2013-03-16 17:53 ` jsm28 at gcc dot gnu.org
2013-09-02 14:52 ` jsm28 at gcc dot gnu.org
2013-11-01 19:01 ` cvs-commit at gcc dot gnu.org
2013-11-21 17:15 ` cvs-commit at gcc dot gnu.org
2014-06-13 10:48 ` fweimer at redhat 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-14155-131-6Gns3mAquR@http.sourceware.org/bugzilla/ \
    --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).