public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vincent-srcware at vinc17 dot net" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug math/13381] rounding problem wih sincosl
Date: Fri, 23 Dec 2011 11:02:00 -0000	[thread overview]
Message-ID: <bug-13381-131-llXWtD6rFI@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13381-131@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=13381

--- Comment #10 from Vincent Lefèvre <vincent-srcware at vinc17 dot net> 2011-12-23 11:01:30 UTC ---
I agree that this bug here can be seen as invalid, as long as the error is not
greater than the documented error bound. It's even "normal" that sincosl
doesn't return the same result as sinl and cosl, as the algorithm is different
and the goal of such a hardware implementation is to provide a result quickly,
though not highly accurate.

Now, there could be two valid related bugs:

1. As these hardware functions seem to be completely wrong for large arguments
(on both Intel and AMD), the glibc should not use them in such cases. At least,
it should provide an option so that it can be compiled to use a software
implementation. Note: though relatively fast hardware range reduction is
possible, I'm sure that was the intent of these hardware instructions when they
were introduced in the 80's (?). I mean that blindly using these hardware
instructions in a system library (i.e. without knowing the application) could
be seen as a misuse of these instructions.

2. The IEEE 754-2008 standard recommends correct rounding. So, a RFE to have
correct rounding would be valid, but perhaps wontfix for the extended precision
(not standard, its primary goal being to ease accurate implementations of the
double precision). For the double precision, unless this has been fixed, sincos
is affected by this problem, which affects code using sin and cos compiled by
GCC; see

  http://www.vinc17.net/research/slides/sieste2010.pdf

Slides 11-15 for this point.

-- 
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.


  parent reply	other threads:[~2011-12-23 11:02 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-04 12:51 [Bug math/13381] New: " gastineau at imcce dot fr
2011-11-07 16:18 ` [Bug math/13381] " gastineau at imcce dot fr
2011-11-08  7:47 ` schwab@linux-m68k.org
2011-11-08  8:36 ` gastineau at imcce dot fr
2011-11-08  8:59 ` schwab@linux-m68k.org
2011-11-09  0:49 ` vincent-srcware at vinc17 dot net
2011-12-22 16:34 ` drepper.fsp at gmail dot com
2011-12-22 16:49 ` gastineau at imcce dot fr
2011-12-22 17:45 ` drepper.fsp at gmail dot com
2011-12-22 19:32 ` gastineau at imcce dot fr
2011-12-23 11:02 ` vincent-srcware at vinc17 dot net [this message]
2011-12-23 11:21 ` gastineau at imcce dot fr
2011-12-23 11:42 ` vincent-srcware at vinc17 dot net
2012-01-09 20:03 ` martyn.j.corden at intel dot com
2012-02-03 14:50 ` vincent-srcware at vinc17 dot net
2014-06-27 11:39 ` 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-13381-131-llXWtD6rFI@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).