public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug math/16447] erfc (0x6.a8p+4) ldbl-128 throws underflow exception
Date: Thu, 06 Feb 2014 16:38:00 -0000	[thread overview]
Message-ID: <bug-16447-131-1XkOpTF8cs@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16447-131@http.sourceware.org/bugzilla/>

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

--- Comment #4 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
On Thu, 6 Feb 2014, stli at linux dot vnet.ibm.com wrote:

> unsafe = abs(n_i) >= -16363; 

Well, abs >= (negative value) doesn't seem right.

To work out what's unsafe, you need to consider how small x22 can be in 
cases where ex2_u.d is small.  The answer is roughly that x22, if not 0, 
is at least 1ulp of the input (not exactly, because of the way values from 
a table get subtracted from the input) - so, roughly, you could have 
problems up to n_i around -16382 + 113.  Certainly saying unsafe = abs 
(n_i) >= 15000 should be safe, even allowing for the way x gets adjusted.

> How to handle the unsafe-check?
> Which platform uses this implementation of expl?
> Can we simply change the unsafe-check in sysdeps/iee754 or is a new
> platform-specific implementation required?

The same correction should apply to all platforms using ldbl-128; no 
platform-specific implementation should be needed.

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


  parent reply	other threads:[~2014-02-06 16:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-16447-131@http.sourceware.org/bugzilla/>
2014-02-04 16:04 ` joseph at codesourcery dot com
2014-02-06 15:57 ` stli at linux dot vnet.ibm.com
2014-02-06 16:38 ` joseph at codesourcery dot com [this message]
2014-02-11 12:53 ` cvs-commit at gcc dot gnu.org
2014-02-11 14:13 ` krebbel1 at de dot ibm.com
2014-06-13  8:58 ` 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-16447-131-1XkOpTF8cs@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).