public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jsm28 at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug math/16338] New: ldbl-128 logl does not handle subnormals Date: Wed, 18 Dec 2013 00:03:00 -0000 [thread overview] Message-ID: <bug-16338-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=16338 Bug ID: 16338 Summary: ldbl-128 logl does not handle subnormals Product: glibc Version: 2.19 Status: NEW Severity: normal Priority: P2 Component: math Assignee: unassigned at sourceware dot org Reporter: jsm28 at gcc dot gnu.org The ldbl-128 logl implementation treats subnormals as if their exponent is normal, resulting in large errors (e.g. logl (0x1p-16494L) is -0x1.62dea45ee3e064dbc66918126b26p+13 when it should be -0x1.6546282207802c89d24d65e96274p+13). I think this is in turn the cause of large lgammal errors in libm testing. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2013-12-18 0:03 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-12-18 0:03 jsm28 at gcc dot gnu.org [this message] 2013-12-18 11:49 ` [Bug math/16338] " jsm28 at gcc dot gnu.org 2014-06-13 9:30 ` 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-16338-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: 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).