public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "thenlich at users dot sourceforge.net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/47945] REAL(8) output conversion error on MinGW32
Date: Tue, 01 Mar 2011 14:45:00 -0000 [thread overview]
Message-ID: <bug-47945-4-ZS1NKD9b2C@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47945-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47945
--- Comment #4 from Thomas Henlich <thenlich at users dot sourceforge.net> 2011-03-01 14:44:54 UTC ---
(In reply to comment #3)
> 0.14285714285714284921875000000000 is still within the accuracy of IEEE double.
> All numbers map to the same IEEE double.
This is technically correct; however a program should also observe portability
and usability rules and not just pick any number from a valid range, but the
number which is the most useful to the program user: either the one most common
across platforms and other compilers (0.14285714285714284921269268124888) or
the "shortest" one (0.14285714285714285000000000000000).
It is very hard to compare long numeric result listings obtained on different
platforms/compilers if some digits (however insignificant) never match.
next prev parent reply other threads:[~2011-03-01 14:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-01 14:00 [Bug libfortran/47945] New: " thenlich at users dot sourceforge.net
2011-03-01 14:01 ` [Bug libfortran/47945] " thenlich at users dot sourceforge.net
2011-03-01 14:02 ` thenlich at users dot sourceforge.net
2011-03-01 14:28 ` schwab@linux-m68k.org
2011-03-01 14:45 ` thenlich at users dot sourceforge.net [this message]
2011-03-02 0:22 ` jvdelisle at gcc dot gnu.org
2011-03-02 6:45 ` thenlich at users dot sourceforge.net
2011-03-02 7:14 ` kargl at gcc dot gnu.org
2011-03-02 7:25 ` burnus at gcc dot gnu.org
2011-03-02 13:49 ` thenlich at users dot sourceforge.net
2011-03-02 16:45 ` burnus at gcc dot gnu.org
2011-03-02 17:04 ` burnus at gcc dot gnu.org
2011-03-02 17:54 ` thenlich at users dot sourceforge.net
2011-03-02 18:02 ` burnus at gcc dot gnu.org
2011-03-02 18:17 ` sgk at troutmask dot apl.washington.edu
2011-03-03 14:04 ` jb at gcc dot gnu.org
2011-03-03 14:58 ` thenlich at users dot sourceforge.net
2011-03-04 6:48 ` thenlich at users dot sourceforge.net
2011-03-04 6:53 ` thenlich at users dot sourceforge.net
2011-03-04 6:54 ` thenlich at users dot sourceforge.net
2011-03-04 6:57 ` thenlich at users dot sourceforge.net
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-47945-4-ZS1NKD9b2C@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/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).