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/16770] scalb spurious "invalid" exceptions
Date: Sat, 29 Mar 2014 17:23:00 -0000	[thread overview]
Message-ID: <bug-16770-131-1AoqXH7S7E@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16770-131@http.sourceware.org/bugzilla/>

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

--- 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  ea6029b19c6004c69a9074bf399091bbfbf58a0c (commit)
      from  56737508002f1759da8d4d9944a8e98e58dce917 (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=ea6029b19c6004c69a9074bf399091bbfbf58a0c

commit ea6029b19c6004c69a9074bf399091bbfbf58a0c
Author: Joseph Myers <joseph@codesourcery.com>
Date:   Sat Mar 29 17:22:14 2014 +0000

    Fix scalb spurious "invalid" exceptions (bug 16770).

    This patch fixes bug 16770, spurious "invalid" exceptions from scalb
    when testing whether the second argument is an integer, by inserting
    appropriate range checks to determine whether a cast to int is safe.
    (Note that invalid_fn is a function that handles both nonintegers and
    large integers, distinguishing them reliably using functions such as
    __rint; note also that there are no issues with scalb needing to avoid
    spurious "inexact" exceptions - it's an old-POSIX XSI function, not a
    standard C function bound to an IEEE 754 operation - although the
    return value is still fully determined.)

    Tested x86_64 and x86.

        [BZ #16770]
        * math/e_scalb.c (__ieee754_scalb): Check second argument is not
        too large before casting to int.
        * math/e_scalbf.c (__ieee754_scalbf): Likewise.
        * math/e_scalbl.c (__ieee754_scalbl): Likewise.
        * math/libm-test.inc (scalb_test_data): Add more tests.

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

Summary of changes:
 ChangeLog          |    9 +++++++++
 NEWS               |    2 +-
 math/e_scalb.c     |    2 +-
 math/e_scalbf.c    |    2 +-
 math/e_scalbl.c    |    2 +-
 math/libm-test.inc |   17 +++++++++++++++++
 6 files changed, 30 insertions(+), 4 deletions(-)

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


  parent reply	other threads:[~2014-03-29 17:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-28 21:22 [Bug math/16770] New: " jsm28 at gcc dot gnu.org
2014-03-29 17:23 ` [Bug math/16770] " jsm28 at gcc dot gnu.org
2014-03-29 17:23 ` cvs-commit at gcc dot gnu.org [this message]
2014-06-12 19:51 ` 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-16770-131-1AoqXH7S7E@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).