public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "martyn.j.corden at intel dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug math/13381] rounding problem wih sincosl
Date: Mon, 09 Jan 2012 20:03:00 -0000	[thread overview]
Message-ID: <bug-13381-131-Fr6fpAYWET@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13381-131@http.sourceware.org/bugzilla/>

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

martyn.j.corden at intel dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |martyn.j.corden at intel
                   |                            |dot com

--- Comment #13 from martyn.j.corden at intel dot com 2012-01-09 20:02:37 UTC ---
Yes, this is likely an issue of slightly different algorithms in the math
library. The main purpose of a sincos function is to give results more
quickly/efficiently that two separate calls to sin and cos, and that might be
better achieved with a different algorithm.
      The same issue arose in the math library provided with the Intel
compiler, libimf. Following a customer report, a change was made for version
12.1 of the Intel compiler, (in Intel Composer XE 2011 SP1), so that sincosl
would return the same results as calls to sinl and cosl. Presumably, similar
changes could be made to the GNU libm if this is felt to be an important issue,
otherwise the sincos documentation should be updated to warn of the potential
difference.  If you have access to Intel’s libimf, it is also possible to link
to it when compiling with gcc, to work around this issue.

Martyn Corden      (Intel Developer Support)

-- 
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:[~2012-01-09 20:03 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
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 [this message]
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-Fr6fpAYWET@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).