public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aj at suse dot de" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug math/2154] New: accuracy of cacoshl is bad.
Date: Sun, 15 Jan 2006 18:02:00 -0000	[thread overview]
Message-ID: <20060115180214.2154.aj@suse.de> (raw)

Adding these tests to math/libm-test.inc's cacosh_test gives upto 770 ULPs for
the long double tests:

  TEST_c_c (cacosh, 0.3, 0.4, 0.405112337178030872507338405200229579L,
1.29016676450309079292712537938218583L);
  TEST_c_c (cacosh, -0.3, 0.4, 0.405112337178030872507338405200229579L,
1.85142588908670244553551800389731705L);
  TEST_c_c (cacosh, 0.3, -0.4, 0.405112337178030872507338405200229579L,
-1.29016676450309079292712537938218583L);
  TEST_c_c (cacosh, -0.3, -0.4, 0.405112337178030872507338405200229579L,
-1.85142588908670244553551800389731705L);

the float and double tests pass, just long double has this problem.

-- 
           Summary: accuracy of cacoshl is bad.
           Product: glibc
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: math
        AssignedTo: drepper at redhat dot com
        ReportedBy: aj at suse dot de
                CC: glibc-bugs at sources dot redhat dot com
 GCC build triplet: x86_64-linux-gnu
  GCC host triplet: x86_64-linux-gnu
GCC target triplet: x86_64-linux-gnu


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

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


             reply	other threads:[~2006-01-15 18:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-15 18:02 aj at suse dot de [this message]
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=20060115180214.2154.aj@suse.de \
    --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).