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/16287] ldbl-128 erfl spurious underflows
Date: Tue, 24 Jun 2014 20:58:00 -0000	[thread overview]
Message-ID: <bug-16287-131-ci7MVRhpUF@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16287-131@http.sourceware.org/bugzilla/>

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

--- Comment #1 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  e7dd3c8c1db8c6d293abb995e033893b7328ad19 (commit)
      from  0ea5d373c7984a1da2d0e990c6e78e6d6c24f91b (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=e7dd3c8c1db8c6d293abb995e033893b7328ad19

commit e7dd3c8c1db8c6d293abb995e033893b7328ad19
Author: Joseph Myers <joseph@codesourcery.com>
Date:   Tue Jun 24 20:56:56 2014 +0000

    Fix ldbl-128 erfl spurious underflows (bug 16287).

    This patch fixes bug 16287, spurious underflows from ldbl-128 erfl
    arising from it calling erfcl for arguments with absolute value at
    least 1.0, although for large positive arguments erfcl correctly
    underflows but erfl shouldn't.  The fix is simply to avoid calling
    erfcl, and just return 1, for arguments above a cut-off large enough
    that erfl correctly rounds to-nearest as 1 but not so large that erfcl
    underflows.

    Tested mips64.  Also tested x86_64 and x86 to confirm the new tests
    (taken from the tests of erfc) don't cause any problems there; no ulps
    updates needed.

        [BZ #16287]
        * sysdeps/ieee754/ldbl-128/s_erfl.c (__erfl): Return 1 without
        calling __erfcl for arguments at least 16.
        * math/auto-libm-test-in: Add more tests of erf.
        * math/auto-libm-test-out: Regenerated.

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

Summary of changes:
 ChangeLog                         |    6 +
 NEWS                              |   24 ++--
 math/auto-libm-test-in            |   10 ++
 math/auto-libm-test-out           |  294 +++++++++++++++++++++++++++++++++++++
 sysdeps/ieee754/ldbl-128/s_erfl.c |    2 +
 5 files changed, 324 insertions(+), 12 deletions(-)

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


      parent reply	other threads:[~2014-06-24 20:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-03  1:04 [Bug math/16287] New: " jsm28 at gcc dot gnu.org
2014-06-13 11:49 ` [Bug math/16287] " fweimer at redhat dot com
2014-06-24 20:58 ` jsm28 at gcc dot gnu.org
2014-06-24 20:58 ` cvs-commit at gcc dot gnu.org [this message]

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-16287-131-ci7MVRhpUF@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).