public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "carlos at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug math/15359] Inaccurate cos for IBM long double
Date: Thu, 25 Apr 2013 17:03:00 -0000	[thread overview]
Message-ID: <bug-15359-131-QSLYRIIoPD@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15359-131@http.sourceware.org/bugzilla/>

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

--- Comment #9 from Carlos O'Donell <carlos at redhat dot com> 2013-04-25 17:03:06 UTC ---
(In reply to comment #8)
> It doesn't make sense to use the ulp of a broken implementation.

The implementation isn't broken, it's just inaccurate.

What problems do we have leaving the test in place and using a large ulp value
for IBM long double?

I noticed that Joseph also said he would like to disable cpow once we switch to
accurate ulps since the error in cpow is going to be a huge number of ulps.

Is this just a policy issue? That we disable tests if the ulp values are too
high?

-- 
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:[~2013-04-25 17:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-11 17:43 [Bug math/15359] New: " schwab@linux-m68k.org
2013-04-12  2:25 ` [Bug math/15359] " carlos at redhat dot com
2013-04-12  2:37 ` carlos at redhat dot com
2013-04-12  6:53 ` carlos at redhat dot com
2013-04-12  9:15 ` schwab@linux-m68k.org
2013-04-12 13:52 ` carlos at redhat dot com
2013-04-25  8:36 ` schwab@linux-m68k.org
2013-04-25 16:10 ` carlos at redhat dot com
2013-04-25 16:16 ` schwab@linux-m68k.org
2013-04-25 17:03 ` carlos at redhat dot com [this message]
2013-04-25 17:14 ` schwab@linux-m68k.org
2013-04-25 20:02 ` carlos at redhat dot com
2013-05-09 13:15 ` carlos at redhat dot com
2013-05-09 21:32 ` jsm28 at gcc dot gnu.org
2014-06-13 18:27 ` 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-15359-131-QSLYRIIoPD@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.org \
    /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).