public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jsm28 at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug math/3976] libm rounding modes do not work correctly for many archs
Date: Mon, 05 Mar 2012 12:27:00 -0000 [thread overview]
Message-ID: <bug-3976-131-UVaHqYdtuM@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-3976-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=3976
Joseph Myers <jsm28 at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution| |FIXED
--- Comment #15 from Joseph Myers <jsm28 at gcc dot gnu.org> 2012-03-05 12:27:36 UTC ---
cosh, sinh tests (some errors in round-upward mode up to 27ulp) added by:
commit ca811b2256d2e48c7288219e9e11dcbab3000f19
Author: Joseph Myers <joseph@codesourcery.com>
Date: Mon Mar 5 12:20:24 2012 +0000
Test cosh, sinh in non-default rounding modes (bug 3976).
pow fixed by:
commit b7cd39e8f8c5cf2844f20eb03f545d19c4c25987
Author: Joseph Myers <joseph@codesourcery.com>
Date: Mon Mar 5 12:22:46 2012 +0000
Fix pow in non-default rounding modes (bug 3976).
So all the reported issues are fixed here. If cases are found of functions
that still (in any rounding mode, for any of float, double, long double)
produce wild results or crash with glibc after my patches - or of functions
that should always produce correctly rounded results such as rint, nextafter,
fma, sqrt, that fail to do so (in any rounding mode, for any of float, double,
long double), please file them as separate bugs for each function found to have
a problem.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next prev parent reply other threads:[~2012-03-05 12:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-3976-131@http.sourceware.org/bugzilla/>
2012-02-29 1:16 ` jsm28 at gcc dot gnu.org
2012-02-29 2:35 ` vincent-srcware at vinc17 dot net
2012-02-29 2:54 ` vincent-srcware at vinc17 dot net
2012-03-02 15:17 ` jsm28 at gcc dot gnu.org
2012-03-02 16:05 ` jsm28 at gcc dot gnu.org
2012-03-02 16:09 ` jsm28 at gcc dot gnu.org
2012-03-02 20:56 ` jsm28 at gcc dot gnu.org
2012-03-05 12:27 ` jsm28 at gcc dot gnu.org [this message]
2012-03-05 13:34 ` vincent-srcware at vinc17 dot net
2013-01-10 19:23 ` aj at suse dot de
2014-02-16 19:37 ` jackie.rosen at hushmail dot com
2014-05-28 19:40 ` schwab at sourceware dot org
2007-02-06 13:14 [Bug math/3976] New: " madcoder at debian dot org
2007-02-06 22:13 ` [Bug math/3976] " madcoder at debian dot org
2007-05-18 14:46 ` debian-glibc at lists dot debian dot org
2007-09-19 12:55 ` vincent+libc at vinc17 dot org
2008-02-25 13:12 ` vincent+libc at vinc17 dot org
2008-10-27 8:18 ` c_keil at yahoo dot de
2008-10-27 8:26 ` jakub at redhat dot com
2008-10-27 9:34 ` vincent+libc at vinc17 dot org
2008-10-27 12:43 ` joseph at codesourcery dot com
2010-03-21 22:24 ` vincent+libc at vinc17 dot 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-3976-131-UVaHqYdtuM@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sources.redhat.com \
/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).