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/16564] Bad overflowing log1p results Date: Wed, 14 May 2014 12:39:00 -0000 [thread overview] Message-ID: <bug-16564-131-pnqSJ2LWMj@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-16564-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=16564 --- 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 1a84c3d6d4bc43c92b6531b09d732e2e9c750dea (commit) from 01dbacd22a8d5e0053f8d0cf13a80286b6cfe79b (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=1a84c3d6d4bc43c92b6531b09d732e2e9c750dea commit 1a84c3d6d4bc43c92b6531b09d732e2e9c750dea Author: Joseph Myers <joseph@codesourcery.com> Date: Wed May 14 12:38:56 2014 +0000 Fix log1pl (LDBL_MAX) in FE_UPWARD mode (bug 16564). Bug 16564 is spurious overflow of log1pl (LDBL_MAX) in FE_UPWARD mode, resulting from log1pl adding 1 to its argument (for arguments not close to 0), which overflows in that mode. This patch fixes this by avoiding adding 1 to large arguments (precisely what counts as large depends on the floating-point format). Tested x86_64 and x86, and spot-checked log1pl tests on mips64 and powerpc64. [BZ #16564] * sysdeps/i386/fpu/s_log1pl.S (__log1pl): Do not add 1 to positive arguments with exponent 65 or above. * sysdeps/ieee754/ldbl-128/s_log1pl.c (__log1pl): Do not add 1 to arguments 0x1p113L or above. * sysdeps/ieee754/ldbl-128ibm/s_log1pl.c (__log1pl): Do not add 1 to arguments 0x1p107L or above. * sysdeps/x86_64/fpu/s_log1pl.S (__log1pl): Do not add 1 to positive arguments with exponent 65 or above. * math/auto-libm-test-in: Add more tests of log1p. * math/auto-libm-test-out: Regenerated. ----------------------------------------------------------------------- Summary of changes: ChangeLog | 12 ++ NEWS | 14 +- math/auto-libm-test-in | 8 + math/auto-libm-test-out | 264 ++++++++++++++++++++++++++++++++ sysdeps/i386/fpu/s_log1pl.S | 7 +- sysdeps/ieee754/ldbl-128/s_log1pl.c | 5 +- sysdeps/ieee754/ldbl-128ibm/s_log1pl.c | 5 +- sysdeps/x86_64/fpu/s_log1pl.S | 7 +- 8 files changed, 311 insertions(+), 11 deletions(-) -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2014-05-14 12:39 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-02-12 12:37 [Bug math/16564] New: " zimmerma+gcc at loria dot fr 2014-05-14 12:39 ` cvs-commit at gcc dot gnu.org [this message] 2014-05-14 12:41 ` [Bug math/16564] " jsm28 at gcc dot gnu.org 2014-06-13 8:38 ` 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-16564-131-pnqSJ2LWMj@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).