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@sources.redhat.com Subject: [Bug math/13914] exp10l (-LDBL_MAX) raises spurious OVERFLOW and INVALID exceptions Date: Sun, 06 May 2012 18:25:00 -0000 [thread overview] Message-ID: <bug-13914-131-4zUtvurUBq@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-13914-131@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=13914 Joseph Myers <jsm28 at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #3 from Joseph Myers <jsm28 at gcc dot gnu.org> 2012-05-06 18:25:20 UTC --- Fixed by: commit d8b82cad1b525bdcbfff88d218c7c45032e4a3af Author: Joseph Myers <joseph@codesourcery.com> Date: Sun May 6 18:23:44 2012 +0000 Fix exp10 inaccuracy and exceptions (bugs 13884, 13914). -- 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-05-06 18:25 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-03-27 23:27 [Bug math/13914] New: exp10l (-LDBL_MAX) raises spurious OVERFLOW exception jsm28 at gcc dot gnu.org 2012-03-28 0:23 ` [Bug math/13914] exp10l (-LDBL_MAX) raises spurious OVERFLOW and INVALID exceptions jsm28 at gcc dot gnu.org 2012-03-28 0:27 ` jsm28 at gcc dot gnu.org 2012-05-06 18:25 ` jsm28 at gcc dot gnu.org [this message] 2014-06-26 13:41 ` 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-13914-131-4zUtvurUBq@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).