public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jsm28 at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug math/2154] accuracy of cacoshl is bad. Date: Wed, 22 Feb 2012 22:22:00 -0000 [thread overview] Message-ID: <bug-2154-131-SrFIaHfdvL@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-2154-131@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=2154 Joseph Myers <jsm28 at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|SUSPENDED |RESOLVED Resolution| |INVALID --- Comment #2 from Joseph Myers <jsm28 at gcc dot gnu.org> 2012-02-22 22:22:26 UTC --- The tests given in this bug take the double constants 0.3 and 0.4 and convert them to long double. The results of cacoshl appear to be within a few ULPs of what is expected for those particular long double values, whereas the expectations given in this testcase are the results for infinite-precision constants 0.3 and 0.4 (as opposed to those for values rounded to 53 bits then extended to 64 bits, or rounded directly to 64 bits) - and when your inputs differ by 11 bits from what they were intended to be, 770 ULPs is hardly an unexpected error. So this is not a correct test and there is no sign of undue inaccuracy here (I don't think it's yet expected for complex functions to be last-bit-accurate correctly rounded). -- 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 parent reply other threads:[~2012-02-22 22:22 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-2154-131@http.sourceware.org/bugzilla/> 2012-02-22 22:22 ` jsm28 at gcc dot gnu.org [this message] 2006-01-15 18:02 [Bug math/2154] New: " aj at suse dot de 2006-04-25 18:43 ` [Bug math/2154] " drepper 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-2154-131-SrFIaHfdvL@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: linkBe 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).