public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tprince at computer dot org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug math/13629] clog() returns wrong values around z=1 Date: Fri, 27 Jan 2012 16:00:00 -0000 [thread overview] Message-ID: <bug-13629-131-On6QOmKpSs@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-13629-131@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=13629 Tim Prince <tprince at computer dot org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tprince at computer dot org --- Comment #3 from Tim Prince <tprince at computer dot org> 2012-01-27 16:00:17 UTC --- I ran the TOMS 714 test against glibc-2.12-1.7.el6.x86_64 and Intel libimf (latter requires option -fp-model source). This test doesn't exercise the neighborhood of (1, 0). The only outright failure for glibc came with LOG( 0.1797693+309 0.1797693+309). Otherwise, the maximum errors in each tested region are similar for the two libraries, but the number of unequal comparisons is about 10 times as many for glibc. Comparisons attached: dclog_gf.txt (gfortran/glibc) dclog_if.txt (ifort/imf) -- 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 prev parent reply other threads:[~2012-01-27 16:00 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-01-27 14:12 [Bug math/13629] New: " fxcoudert at gcc dot gnu.org 2012-01-27 15:57 ` [Bug math/13629] " tprince at computer dot org 2012-01-27 15:58 ` tprince at computer dot org 2012-01-27 16:00 ` tprince at computer dot org [this message] 2012-03-03 21:28 ` jsm28 at gcc dot gnu.org 2012-03-20 0:39 ` jsm28 at gcc dot gnu.org 2012-07-26 11:36 ` jsm28 at gcc dot gnu.org 2012-07-31 14:26 ` jsm28 at gcc dot gnu.org 2012-09-25 19:49 ` jsm28 at gcc dot gnu.org 2014-06-27 10:03 ` 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-13629-131-On6QOmKpSs@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).