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/19032] [i386] acosh (-qNaN) spurious "invalid" exception
Date: Wed, 30 Sep 2015 21:45:00 -0000	[thread overview]
Message-ID: <bug-19032-131-5aylxFqLnu@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-19032-131@http.sourceware.org/bugzilla/>

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

--- Comment #2 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  8c6c9236361fbc077769673c259828216403bc33 (commit)
      from  93e448cbed1095c88133f2a304b1bbba72e480af (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=8c6c9236361fbc077769673c259828216403bc33

commit 8c6c9236361fbc077769673c259828216403bc33
Author: Joseph Myers <joseph@codesourcery.com>
Date:   Wed Sep 30 21:44:42 2015 +0000

    Fix i386 acosh (-qNaN) spurious "invalid" exception.

    The i386 versions of acoshf and acosh raise a spurious "invalid"
    exception for an argument that is a quiet NaN with the sign bit set.
    The integer arithmetic to detect arguments < 1 also detects -NaN, and
    then the computation 0 / 0 in that case raises the exception.  This
    patch fixes this by using (x - x) / (x - x) as the computation in that
    case instead, which will always raise the exception for non-NaN
    arguments reaching that code, but not for quiet NaN arguments.

    Tested for x86_64 and x86.

        [BZ #19032]
        * sysdeps/i386/fpu/e_acosh.S (__ieee754_acosh): For arguments < 1,
        compute result as (x - x) / (x - x) not as 0 / 0.
        * sysdeps/i386/fpu/e_acoshf.S (__ieee754_acoshf): Likewise.
        * math/libm-test.inc (acosh_test_data): Add another test of acosh.

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

Summary of changes:
 ChangeLog                   |    6 ++++++
 NEWS                        |    2 +-
 math/libm-test.inc          |    1 +
 sysdeps/i386/fpu/e_acosh.S  |    5 +++--
 sysdeps/i386/fpu/e_acoshf.S |    5 +++--
 5 files changed, 14 insertions(+), 5 deletions(-)

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


  parent reply	other threads:[~2015-09-30 21:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-30 17:50 [Bug math/19032] New: " jsm28 at gcc dot gnu.org
2015-09-30 18:07 ` [Bug math/19032] " cvs-commit at gcc dot gnu.org
2015-09-30 21:45 ` cvs-commit at gcc dot gnu.org [this message]
2015-09-30 21:46 ` jsm28 at gcc dot gnu.org

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-19032-131-5aylxFqLnu@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).