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/16619] [ldbl-128ibm] frexpl bad results on some denormal arguments
Date: Wed, 26 Nov 2014 13:56:00 -0000	[thread overview]
Message-ID: <bug-16619-131-bc54zY64yn@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16619-131@http.sourceware.org/bugzilla/>

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

--- Comment #5 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  706688aaefdeb48e63519525f11108ce14844a26 (commit)
      from  12da14a59135fe331f294b91488c1bdf55b35b4e (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=706688aaefdeb48e63519525f11108ce14844a26

commit 706688aaefdeb48e63519525f11108ce14844a26
Author: Joseph Myers <joseph@codesourcery.com>
Date:   Wed Nov 26 13:54:55 2014 +0000

    FIx ldbl-128ibm frexpl for 32-bit systems (bug 16619, bug 16740).

    This patch fixes bugs in ldbl-128ibm frexpl for 32-bit systems shown
    up by warnings:

    ../sysdeps/ieee754/ldbl-128ibm/s_frexpl.c:82:4: warning: left shift count
>= width of type
    ../sysdeps/ieee754/ldbl-128ibm/s_frexpl.c:129:5: warning: left shift count
>= width of type

    This did in fact show up in test-ldouble.out (alongside all the other
    problems there ... maybe we should again consider running the libm
    tests at finer granularity from the makefiles) as already covered by
    the testsuite after the previous patch that fixed these bugs for
    64-bit systems.  The fix is simply using 1LL instead of 1L when
    shifting by 52.

    Tested for powerpc32 (soft float).

        [BZ #16619]
        [BZ #16740]
        * sysdeps/ieee754/ldbl-128ibm/s_frexpl.c (__frexpl): Use 1LL << 52
        instead of 1L << 52.

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

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

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


  parent reply	other threads:[~2014-11-26 13:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-21  2:08 [Bug math/16619] New: " jsm28 at gcc dot gnu.org
2014-03-25 14:20 ` [Bug math/16619] " amodra at gmail dot com
2014-04-16 10:05 ` cvs-commit at gcc dot gnu.org
2014-04-16 10:19 ` amodra at gmail dot com
2014-04-25 17:02 ` cvs-commit at gcc dot gnu.org
2014-06-13  8:10 ` fweimer at redhat dot com
2014-11-26 13:56 ` cvs-commit at gcc dot gnu.org [this message]
2015-01-16 17:03 ` cvs-commit at gcc dot gnu.org
2015-02-23 14:23 ` cvs-commit 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-16619-131-bc54zY64yn@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).