public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "calixte.denizet@scilab-enterprises.com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug math/706] pow() produces inaccurate results for base ~ 1.0, and large exponent on 32-bit x86
Date: Tue, 28 Feb 2012 12:35:00 -0000 [thread overview]
Message-ID: <bug-706-131-dVdjDJpjF4@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-706-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=706
Calixte <calixte.denizet@scilab-enterprises.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |calixte.denizet@scilab-ente
| |rprises.com
--- Comment #11 from Calixte <calixte.denizet@scilab-enterprises.com> 2012-02-28 12:34:51 UTC ---
Clearly the pow alogrithm should be reimplemented with a better one.
What I proposed is just an easy workaround which can be easily and quickly
implemented (and it would improve the actual results).
About the char in the C code: it is just used for its sign (+/- 1) not for its
value.
--
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-02-28 12:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-706-131@http.sourceware.org/bugzilla/>
2012-02-14 14:49 ` vincent-srcware at vinc17 dot net
2012-02-22 21:30 ` jsm28 at gcc dot gnu.org
2012-02-22 21:54 ` jsm28 at gcc dot gnu.org
2012-02-25 16:06 ` calixte.denizet@scilab-enterprises.com
2012-02-27 15:41 ` vincent-srcware at vinc17 dot net
2012-02-28 12:35 ` calixte.denizet@scilab-enterprises.com [this message]
2012-02-28 14:04 ` vincent-srcware at vinc17 dot net
2012-02-28 14:59 ` vincent-srcware at vinc17 dot net
2012-02-28 16:36 ` [Bug math/706] pow() produces inaccurate results for base ~ 1.0, and large integer " vincent-srcware at vinc17 dot net
2012-04-09 9:49 ` jsm28 at gcc dot gnu.org
2014-02-16 18:27 ` jackie.rosen at hushmail dot com
2014-05-28 19:45 ` schwab at sourceware dot 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-706-131-dVdjDJpjF4@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).