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/13840] hypotf overflow and underflow
Date: Wed, 14 Mar 2012 01:21:00 -0000 [thread overview]
Message-ID: <bug-13840-131-MD1y5g0eOW@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13840-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=13840
Joseph Myers <jsm28 at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
--- Comment #1 from Joseph Myers <jsm28 at gcc dot gnu.org> 2012-03-14 01:20:44 UTC ---
Fixed by:
commit 7c10fd3515f983ca732b2166ccffebbf83603f1f
Author: David S. Miller <davem@davemloft.net>
Date: Tue Mar 13 18:08:58 2012 -0700
Fix hypotf overflow/underflow by using double precision instead of scaling.
[BZ #13840]
* sysdeps/ieee754/flt-32/e_hypotf.c (__ieee754_hypotf): Rewrite to use
double-precision for the calculation instead of scaling.
Testcases added by:
commit aa4a2ae1dbc2c7a3469ec13610f0d7a84e3bfc79
Author: Joseph Myers <joseph@codesourcery.com>
Date: Wed Mar 14 01:12:05 2012 +0000
Add tests for hypot overflow/underflow.
--
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-03-14 1:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-13 20:39 [Bug math/13840] New: " jsm28 at gcc dot gnu.org
2012-03-14 1:21 ` jsm28 at gcc dot gnu.org [this message]
2014-06-26 13:59 ` [Bug math/13840] " 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-13840-131-MD1y5g0eOW@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: 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).