public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "grugh at centrum dot cz" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug math/5781] Slow sine function for special values on AMD64 - second attempt
Date: Fri, 22 Feb 2008 09:01:00 -0000	[thread overview]
Message-ID: <20080222090056.16615.qmail@sourceware.org> (raw)
In-Reply-To: <20080221091038.5781.grugh@centrum.cz>


------- Additional Comments From grugh at centrum dot cz  2008-02-22 09:00 -------
Is there any compile flag or #define, which can disable the <=0.5 ulp precision
and the math sin function will use only the fast built-in fp intructions?
For our real-time software it is necessary to be "quick", the ultra precision
has low priority.
Now we are using a workaround: I can put the original argument to long double
variable and call sinl function with long double result. Both, the new argument
and the result, have to be volatile to disable the compiler optimization of it
(probably uses the "fast" sin instead).

Results of sin(0.93340582292648832662962377071381)
----------------------------------------------------
distr function    value                    result_type printf_format
--------------------------------------------------------------------
32 sin  0.80365140438773496889268699305831 double      "%.32g"
32 sinl 0.80365140438773496889268699305831 double      "%.32g"
32 sinl 0.80365140438773491338153576180048 long double "%.32Lg

64 sin  0.80365140438773485787038453054265 double      "%.32g"
 (~ -5.5511151231257827021181583404541e-17 difference from 80bit value)
64 sinl 0.80365140438773496889268699305831 double      "%.32g"
 (~ +5.5511151231257827021181583404541e-17 difference from 80bit value )
64 sinl 0.80365140438773491338153576180048 long double "%.32Lg"


-- 


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

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


  parent reply	other threads:[~2008-02-22  9:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-21  9:11 [Bug math/5781] New: " grugh at centrum dot cz
2008-02-21  9:39 ` [Bug math/5781] " jakub at redhat dot com
2008-02-21 17:10 ` joseph at codesourcery dot com
2008-02-21 17:43 ` jakub at redhat dot com
2008-02-22  9:01 ` grugh at centrum dot cz [this message]
2008-07-14 14:17 ` grugh at centrum dot cz
     [not found] <bug-5781-131@http.sourceware.org/bugzilla/>
2012-02-29 20:20 ` jsm28 at gcc dot gnu.org
2013-04-01 12:54 ` siddhesh at redhat dot com
2013-04-10  4:25 ` siddhesh at redhat dot com
2013-12-03 18:40 ` jsm28 at gcc dot gnu.org
2014-02-05 21:07 ` john.wilkinson at spirent dot com
2014-02-06  7:40 ` john.wilkinson at spirent dot com
2014-02-06 15:48 ` carlos 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=20080222090056.16615.qmail@sourceware.org \
    --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).