From: me22 <me22.ca@gmail.com>
To: Jonathan <jsealy@cwgsy.net>
Cc: gcc-help@gcc.gnu.org
Subject: Re: surprising precision
Date: Wed, 03 Mar 2010 20:52:00 -0000 [thread overview]
Message-ID: <fa28b9251003031251y395b452crda964c43ad1d1ed8@mail.gmail.com> (raw)
In-Reply-To: <D5846594-AE6E-4BCD-B81E-6D8DB68EB780@cwgsy.net>
On 3 March 2010 15:29, Jonathan <jsealy@cwgsy.net> wrote:
> It has not received any explanations yet.
> On the one hand it appears not to be a problem but on the other hand could
> be a spectacular bug.
>
It's probably just you not understanding what floating point numbers are.
Go read http://en.wikipedia.org/wiki/IEEE_754-2008
next prev parent reply other threads:[~2010-03-03 20:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-03 20:29 Jonathan
2010-03-03 20:42 ` Andrew Haley
2010-03-03 20:52 ` me22 [this message]
2010-03-03 21:58 ` Bob Plantz
2010-03-03 21:53 ` John S. Fine
2010-03-04 15:54 ` Steve Teale
2010-03-04 16:55 ` Andrew Haley
2010-03-04 17:28 ` Bob Plantz
2010-03-04 18:34 ` Dean Anderson
2010-03-05 15:59 ` Ian Lance Taylor
2010-03-05 16:58 ` John S. Fine
2010-03-05 19:42 ` Steve Teale
2010-03-03 22:03 ` Bob Plantz
2010-03-04 18:41 ` Toon Moene
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=fa28b9251003031251y395b452crda964c43ad1d1ed8@mail.gmail.com \
--to=me22.ca@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=jsealy@cwgsy.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).