public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "stli at linux dot vnet.ibm.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 15:57:00 -0000	[thread overview]
Message-ID: <bug-16447-131-Ha8eN1rQfj@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16447-131@http.sourceware.org/bugzilla/>

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

--- Comment #3 from Stefan Liebler <stli at linux dot vnet.ibm.com> ---
I´ve posted a patch for the exp testcase (expl(-11342.8125)).
I´ve also tested a wider unsafe-check:
unsafe = abs(n_i) >= -16363; 
//unsafe = abs(n_i) >= -LDBL_MIN_EXP - 1;
Then the testcase passes on S/390.
LDBL_MIN_EXP expands to -16381 on S/390.

A small test on S/390 shows that 
expl(-11341.99999L) works as expected, but with
expl(-11341.999999L) the result is same as expl(-11342.8125).
In both cases n_i == -16363.

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?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
>From glibc-bugs-return-21121-listarch-glibc-bugs=sources.redhat.com@sourceware.org Thu Feb 06 16:07:36 2014
Return-Path: <glibc-bugs-return-21121-listarch-glibc-bugs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-glibc-bugs@sources.redhat.com
Received: (qmail 31705 invoked by alias); 6 Feb 2014 16:07:35 -0000
Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <glibc-bugs.sourceware.org>
List-Subscribe: <mailto:glibc-bugs-subscribe@sourceware.org>
List-Post: <mailto:glibc-bugs@sourceware.org>
List-Help: <mailto:glibc-bugs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: glibc-bugs-owner@sourceware.org
Delivered-To: mailing list glibc-bugs@sourceware.org
Received: (qmail 31617 invoked by uid 48); 6 Feb 2014 16:07:30 -0000
From: "carlos at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug network/16529] netinet/in.h breaks -pedantic
Date: Thu, 06 Feb 2014 16:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: glibc
X-Bugzilla-Component: network
X-Bugzilla-Version: unspecified
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: carlos at redhat dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-16529-131-9I5hMOhd1k@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-16529-131@http.sourceware.org/bugzilla/>
References: <bug-16529-131@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-02/txt/msg00098.txt.bz2
Content-length: 541

https://sourceware.org/bugzilla/show_bug.cgi?id\x16529

Carlos O'Donell <carlos at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |carlos at redhat dot com

--- Comment #4 from Carlos O'Donell <carlos at redhat dot com> ---
This bug is my mistake. I'll remove the trailing comma which is only valid C99.

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


  parent reply	other threads:[~2014-02-06 15:57 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 [this message]
2014-02-06 16:38 ` joseph at codesourcery dot com
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-Ha8eN1rQfj@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).