public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "liubov.dmitrieva at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug math/14283] Inaccurate range reduction for float (sinf, cosf)
Date: Mon, 25 Jun 2012 10:39:00 -0000 [thread overview]
Message-ID: <bug-14283-131-bvSmOVfvog@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-14283-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=14283
Liubov Dmitrieva <liubov.dmitrieva at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |liubov.dmitrieva at gmail
| |dot com
Resolution| |FIXED
--- Comment #1 from Liubov Dmitrieva <liubov.dmitrieva at gmail dot com> 2012-06-25 10:38:25 UTC ---
The patch works well.
Before patch <http://sourceware.org/ml/libc-alpha/2012-06/msg00650.html>
applied Intel proprietary test framework yields the following results:
On I386:
Summary:
----------------------------------
Function PASS/ Max Ulp Roun
FAIL error ding
----------------------------------
SINF FAIL 6.987e+06 Near
SINF FAIL 2.334e+07 +Inf
SINF FAIL 1.191e+07 -Inf
SINF FAIL 2.229e+06 Zero
----------------------------------
COSF FAIL 1.141e+05 Near
COSF FAIL 4.102e+05 +Inf
COSF FAIL 2.003e+05 -Inf
COSF FAIL 27.631139 Zero
----------------------------------
On x86_64:
Summary:
----------------------------------
Function PASS/ Max Ulp Roun
FAIL error ding
----------------------------------
SINF FAIL 7.390e+06 Near
SINF FAIL 2.054e+07 +Inf
SINF FAIL 3.759e+06 -Inf
SINF FAIL 3.759e+06 Zero
----------------------------------
COSF FAIL 2.489e+05 Near
COSF FAIL 2.754e+05 +Inf
COSF FAIL 2.754e+05 -Inf
COSF FAIL 2.754e+05 Zero
----------------------------------
I applied the patch, and results now good (I allowed error 5 ulp, hence no
errors):
On I386:
Summary:
----------------------------------
Function PASS/ Max Ulp Roun
FAIL error ding
----------------------------------
SINF PASS 0.949884 Near
SINF PASS 1.501194 +Inf
SINF PASS 1.542971 -Inf
SINF PASS 1.542971 Zero
----------------------------------
COSF PASS 2.905172 Near
COSF PASS 2.905172 +Inf
COSF PASS 3.905172 -Inf
COSF PASS 3.905172 Zero
----------------------------------
On x86_64:
Summary:
----------------------------------
Function PASS/ Max Ulp Roun
FAIL error ding
----------------------------------
SINF PASS 1.213484 Near
SINF PASS 3.542971 +Inf
SINF PASS 1.854113 -Inf
SINF PASS 1.875448 Zero
----------------------------------
COSF PASS 2.905172 Near
COSF PASS 3.544283 +Inf
COSF PASS 3.905172 -Inf
COSF PASS 3.905172 Zero
----------------------------------
--
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-06-25 10:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-22 20:40 [Bug math/14283] New: " jsm28 at gcc dot gnu.org
2012-06-25 10:39 ` liubov.dmitrieva at gmail dot com [this message]
2012-06-25 10:56 ` [Bug math/14283] " jsm28 at gcc dot gnu.org
2012-07-03 17:13 ` jsm28 at gcc dot gnu.org
2013-04-23 9:38 ` siddhesh at redhat dot com
2014-06-13 18:19 ` 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-14283-131-bvSmOVfvog@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).