public inbox for gsl-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Thanh Vo <thanhvv@gmail.com>
To: gsl-discuss@sourceware.org, bug-gsl@gnu.org
Cc: "Earl T. Barr" <etbarr@ucdavis.edu>,
	Zhendong Su <su@cs.ucdavis.edu>, Brian Gough <bjg@gnu.org>
Subject: Floating-point exceptions in the GSL
Date: Fri, 04 Mar 2011 08:32:00 -0000	[thread overview]
Message-ID: <AANLkTik2LsMObrXxiMcVzbP1ysmarmbSpmEZwm8rACW9@mail.gmail.com> (raw)

Hi,

My name's Thanh Vo. My research group is developing a tool to detect
floating point exceptions in numerical code. On Aug 11th 2010, we contacted
the list to report exception triggering inputs we had found in the GSL.
Brian Gough confirmed the exceptions were valid warnings.  We have continued
our work since then.  In this email, we report more, potentially problematic
exception-triggering inputs.

For each exception, we describe the name of function, the type of exception
thrown, the inputs that trigger the exception, and the source line that
throws the exception.

1.  gsl_sf_bessel_Inu_scaled_asymp_unif_e
Invalid: nu = 0.000000e+00 and  x = 0.000000e+00
Location: line 359 at bessel.c

2.  fg_asymp
Divide ByZero: x = 0.000000e+00
Location:  line 228 at sinint.c

3.  gsl_sf_legendre_P3
Overflow: x = -5.996154e+153
Location: line 95 at legendre_poly.c

4.  gsl_sf_gammastar
Underflow: x = 8.988466e+307
Location: line 1342 at gamma.c

You can see the full list of potential bugs at

barr.softwareprocess.es

If anyone could confirm whether any of these exceptions are useful warnings
or actual bugs, we would appreciate it.

We are finishing the tool and will release it as open source after
publishing the results.

Looking forward to hearing from you,

Best regards,

Thanh Vo.

                 reply	other threads:[~2011-03-04  8:32 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=AANLkTik2LsMObrXxiMcVzbP1ysmarmbSpmEZwm8rACW9@mail.gmail.com \
    --to=thanhvv@gmail.com \
    --cc=bjg@gnu.org \
    --cc=bug-gsl@gnu.org \
    --cc=etbarr@ucdavis.edu \
    --cc=gsl-discuss@sourceware.org \
    --cc=su@cs.ucdavis.edu \
    /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).