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/16407] ldbl-128ibm coshl spurious overflows
Date: Tue, 07 Jan 2014 22:00:00 -0000	[thread overview]
Message-ID: <bug-16407-131-vQsB4zv4tP@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16407-131@http.sourceware.org/bugzilla/>

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

--- 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  b821f414e480d7f9e097fa453b1c9bfd44d64316 (commit)
      from  196f456b842ee96e1bf1e5ae6ed21ba427dee3f3 (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=b821f414e480d7f9e097fa453b1c9bfd44d64316

commit b821f414e480d7f9e097fa453b1c9bfd44d64316
Author: Joseph Myers <joseph@codesourcery.com>
Date:   Tue Jan 7 22:00:04 2014 +0000

    Fix ldbl-128ibm coshl spurious overflows (bug 16407).

    This patch fixes bug 16407, spurious overflows from ldbl-128ibm coshl.
    The implementation assumed that a high part (reinterpreted as an
    integer) of the absolute value of the argument of 0x408633ce8fb9f87dLL
    or more meant overflow, but the actual threshold has high part
    0x408633ce8fb9f87eLL (and a negative low part).  The patch adjusts the
    threshold accordingly.

    sinhl probably has the same issue, but I didn't get that far in adding
    tests of special cases (such as just below and above overflow) before
    the freeze and during the freeze is not a suitable time to add them
    (as they'd require ulps to be regenerated again), so I'm not changing
    that function for now; when I add more tests of special cases, we'll
    discover whether sinhl indeed has this problem.

    Tested powerpc32.

        * sysdeps/ieee754/ldbl-128ibm/e_coshl.c (__ieee754_coshl):
        Increase overflow threshold.

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

Summary of changes:
 ChangeLog                             |    6 ++++++
 NEWS                                  |    2 +-
 sysdeps/ieee754/ldbl-128ibm/e_coshl.c |    2 +-
 3 files changed, 8 insertions(+), 2 deletions(-)

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


  reply	other threads:[~2014-01-07 22:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-07 20:51 [Bug math/16407] New: " jsm28 at gcc dot gnu.org
2014-01-07 22:00 ` cvs-commit at gcc dot gnu.org [this message]
2014-01-07 22:01 ` [Bug math/16407] " jsm28 at gcc dot gnu.org
2014-06-13  9:11 ` 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-16407-131-vQsB4zv4tP@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).