public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ices.utexas.edu>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: optimization/10772: Result differences between debug and optmize libs on linux; and with sol/nt on optimize mode
Date: Wed, 14 May 2003 20:56:00 -0000 [thread overview]
Message-ID: <20030514205601.18711.qmail@sources.redhat.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 985 bytes --]
The following reply was made to PR optimization/10772; it has been noted by GNATS.
From: Wolfgang Bangerth <bangerth@ices.utexas.edu>
To: omar beo <omarbeo@hotmail.com>
Cc: gcc-bugs@gcc.gnu.org, <gcc-gnats@gcc.gnu.org>
Subject: Re: optimization/10772: Result differences between debug and optmize
libs on linux; and with sol/nt on optimize mode
Date: Wed, 14 May 2003 15:52:52 -0500 (CDT)
> But this did not answer the original question, why I’m not getting the same
> results in the other platforms?
Because x86 has a fundamentally broken floating point model with different
accuracy of floats in registers and in memory. x86 FP computations are
fundamentally unreliable if you're used to thinking in what "decent"
processors do.
W.
-------------------------------------------------------------------------
Wolfgang Bangerth email: bangerth@ices.utexas.edu
www: http://www.ices.utexas.edu/~bangerth/
next reply other threads:[~2003-05-14 20:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-14 20:56 Wolfgang Bangerth [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-14 19:26 omar beo
2003-05-14 15:16 omar beo
2003-05-14 15:14 bangerth
2003-05-14 14:36 Christian Ehrhardt
2003-05-14 10:48 giovannibajo
2003-05-14 6:26 Dara Hazeghi
2003-05-13 18:26 omarbeo
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=20030514205601.18711.qmail@sources.redhat.com \
--to=bangerth@ices.utexas.edu \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@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).