public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dylan-sourceware at dylex dot net" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug math/16545] New: Test failures: small differences in float/double y0, etc.
Date: Sun, 09 Feb 2014 02:38:00 -0000	[thread overview]
Message-ID: <bug-16545-131@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 16545
           Summary: Test failures: small differences in float/double y0,
                    etc.
           Product: glibc
           Version: 2.19
            Status: NEW
          Severity: minor
          Priority: P2
         Component: math
          Assignee: unassigned at sourceware dot org
          Reporter: dylan-sourceware at dylex dot net

Created attachment 7399
  --> http://sourceware.org/bugzilla/attachment.cgi?id=7399&action=edit
cat test-{,i}{double,float}.out

Linux x86_64 3.12.6, gcc 4.8.2, AMD Opteron(tm) Processor 4274 HE, glibc 2.19

I'm seeing failures in the test-float, -double, -ifloat, -idouble tests
producing very small differences (fractional errors at most 1e-7) on my
machine.  No major discrepencies or issues, but I would've expected these to
pass.  Perhaps caused by minor gcc or processor differences?

-- 
You are receiving this mail because:
You are on the CC list for the bug.


             reply	other threads:[~2014-02-09  2:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-09  2:38 dylan-sourceware at dylex dot net [this message]
2014-02-10 15:02 ` [Bug math/16545] " jsm28 at gcc dot gnu.org
2014-02-10 16:48 ` dylan-sourceware at dylex dot net
2014-02-12 15:56 ` cvs-commit at gcc dot gnu.org
2014-02-12 15:59 ` jsm28 at gcc dot gnu.org
2014-02-20  0:55 ` cvs-commit at gcc dot gnu.org

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-16545-131@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).