public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug math/17257] erf generates spurious underflow for long-double-128
Date: Mon, 11 Aug 2014 22:31:00 -0000	[thread overview]
Message-ID: <bug-17257-131-9d78hSYBly@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17257-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=17257

--- Comment #1 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
I do *not* see these on mips64 (n32), for which I'm currently running 
tests (with GCC 4.9, so supporting exceptions for long double).  Such 
failures were supposed to be fixed by the fix for bug 16516; you may have 
some architecture-specific issue here.

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


  reply	other threads:[~2014-08-11 22:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-11 22:05 [Bug math/17257] New: " davem at davemloft dot net
2014-08-11 22:31 ` joseph at codesourcery dot com [this message]
2015-09-15 16:23 ` [Bug math/17257] [sparc] " jsm28 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-17257-131-9d78hSYBly@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).