public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gastineau at imcce dot fr" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug math/13381] rounding problem wih sincosl
Date: Thu, 22 Dec 2011 19:32:00 -0000	[thread overview]
Message-ID: <bug-13381-131-8gljJD95yN@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 #9 from gastineau at imcce dot fr 2011-12-22 19:31:39 UTC ---
The current glibc documentation says :

In many applications where sin and cos are used, the sine and cosine of the
same angle are needed at the same time. It is more efficient to compute them
simultaneously, so the library provides a 
function to do that.

— Function: void sincos (double x, double *sinx, double *cosx)
— Function: void sincosf (float x, float *sinx, float *cosx)
— Function: void sincosl (long double x, long double *sinx, long double *cosx)
These functions return the sine of x in *sinx and the cosine of x in *cos,
where x is given in radians. Both values, *sinx and *cosx, are in the range of
-1 to 1.

This function is a GNU extension. Portable programs should be prepared to cope
with its absence.



So, if it's a GNU extension, it's not of the responsability of the user to
check that it gives a different result, as the documentation says no thing
about the implementation.

Mickaël




Le 22/12/11 18:45, drepper.fsp at gmail dot com a écrit :
> http://sourceware.org/bugzilla/show_bug.cgi?id=13381
>
> Ulrich Drepper<drepper.fsp at gmail dot com>  changed:
>
>             What    |Removed                     |Added
> ----------------------------------------------------------------------------
>               Status|REOPENED                    |RESOLVED
>           Resolution|                            |INVALID
>
> --- Comment #8 from Ulrich Drepper<drepper.fsp at gmail dot com>  2011-12-22 17:45:01 UTC ---
> If you don't understand how computers work then don't bother other people.  The
> function is implemented by a single instruction.  It's entire Intel's
> responsibility to provide the result.
>

-- 
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-22 19:32 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 [this message]
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
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-8gljJD95yN@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).