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/16315] Bad overflowing pow results for directed rounding Date: Sun, 29 Jun 2014 11:50:00 -0000 [thread overview] Message-ID: <bug-16315-131-2sjUVWTqdW@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-16315-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=16315 --- 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 edea402804bce917cfd7cd1af76212e6364c23db (commit) from dd0ba018122e88937a5f14b6594b9a40693b2e58 (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=edea402804bce917cfd7cd1af76212e6364c23db commit edea402804bce917cfd7cd1af76212e6364c23db Author: Joseph Myers <joseph@codesourcery.com> Date: Sun Jun 29 11:49:08 2014 +0000 Fix ldbl-128 powl sign of result in overflow / underflow cases (bug 17097). This patch fixes bug 17097, ldbl-128 powl producing overflowing / underflowing results with positive sign when the result should have been negative. This was shown up by the tests in non-default rounding modes added by my patch for bug 16315, but isn't actually limited to non-default rounding modes: rather, when rounding to nearest the wrappers produced a result with the correct sign and so always hid the bug unless -lieee was used to disable the wrappers. The problem is that in the cases where Y is large enough that the result overflows or underflows for X not very close to 1, but not large enough to overflow or underflow for all X != +/- 1 (in the latter case Y is always an even integer), a positive overflowing / underflowing result is always returned, rather than one with the correct sign. This patch moves the relevant part of computation of the sign earlier and returns a result of the correct sign. Tested for mips64. [BZ #17097] * sysdeps/ieee754/ldbl-128/e_powl.c (__ieee754_powl): Return result with correct sign in case of exponents that produce overflow except for X very close to 1. ----------------------------------------------------------------------- Summary of changes: ChangeLog | 7 +++++++ NEWS | 2 +- sysdeps/ieee754/ldbl-128/e_powl.c | 26 +++++++++++++------------- 3 files changed, 21 insertions(+), 14 deletions(-) -- You are receiving this mail because: You are on the CC list for the bug.
prev parent reply other threads:[~2014-06-29 11:50 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-12-11 1:00 [Bug math/16315] New: " jsm28 at gcc dot gnu.org 2013-12-11 1:22 ` [Bug math/16315] " jsm28 at gcc dot gnu.org 2014-03-21 0:04 ` cvs-commit at gcc dot gnu.org 2014-06-13 11:25 ` fweimer at redhat dot com 2014-06-23 20:14 ` cvs-commit at gcc dot gnu.org 2014-06-23 20:14 ` jsm28 at gcc dot gnu.org 2014-06-29 11:50 ` 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-16315-131-2sjUVWTqdW@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: linkBe 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).