From: Richard Henderson <rth@redhat.com>
To: Stephen L Moshier <steve@moshier.net>
Cc: gcc@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: real_to_decimal rounds incorrectly
Date: Sun, 20 Oct 2002 14:55:00 -0000 [thread overview]
Message-ID: <20021019224733.GC30204@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0210191305040.1558-100000@moshier.net>
On Sat, Oct 19, 2002 at 01:54:47PM -0400, Stephen L Moshier wrote:
> IEEE-specific modifications were taken from the IEEE spec.
> Other than that, I draw a blank on references. It's just arithmetic.
By inference, it appears to be (a variation of) Steele & White's 1990
algorithm.
I havn't been able to get hold of the original paper, not being an
ACM member, but I've found a few papers that expand on Steele & White's,
and which give a description good enough to recognize the salient points.
r~
next prev parent reply other threads:[~2002-10-19 22:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-15 14:34 Stephen L Moshier
2002-10-18 19:54 ` Richard Henderson
2002-10-19 15:47 ` Stephen L Moshier
2002-10-20 14:55 ` Richard Henderson [this message]
2002-10-20 15:34 ` Stephen L Moshier
2002-10-21 15:59 ` Stephen L Moshier
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=20021019224733.GC30204@redhat.com \
--to=rth@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=steve@moshier.net \
/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).