public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Toon Moene <toon@moene.indiv.nluug.nl> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c/8395: gcc 2.95.4 and 3.2 generate wrong code for double on intel Date: Sat, 02 Nov 2002 07:56:00 -0000 [thread overview] Message-ID: <20021102155601.28368.qmail@sources.redhat.com> (raw) The following reply was made to PR c/8395; it has been noted by GNATS. From: Toon Moene <toon@moene.indiv.nluug.nl> To: Marco Bernardo <bernardo@sti.uniurb.it> Cc: Bruce Allen <ballen@gravity.phys.uwm.edu>, Bruce Allen <ballen@aei.mpg.de>, gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org Subject: Re: c/8395: gcc 2.95.4 and 3.2 generate wrong code for double on intel Date: Sat, 02 Nov 2002 16:56:04 +0100 Marco Bernardo wrote: > 1. Some colleagues of mine tried to compile and run the same program > on other platforms, in particular on a sparc machine, and the output > turned out to be > -6 -1.2 5 0 -6 0 > Why is that? Isn't the IEEE 754 standard adopted on sparc machines? Yes. For further explanations, see the "Further Readings" item on our home page: http://gcc.gnu.org -> "Further Readings" (left column) -> Differences among IEEE 754 implementations (by Doug Priest) -- Toon Moene - mailto:toon@moene.indiv.nluug.nl - phoneto: +31 346 214290 Saturnushof 14, 3738 XG Maartensdijk, The Netherlands Maintainer, GNU Fortran 77: http://gcc.gnu.org/onlinedocs/g77_news.html Join GNU Fortran 95: http://g95.sourceforge.net/ (under construction)
next reply other threads:[~2002-11-02 15:56 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-11-02 7:56 Toon Moene [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-11-04 9:06 Joseph S. Myers 2002-11-04 9:06 Marco Bernardo 2002-11-04 3:06 Bruce Allen 2002-11-02 22:26 Bruce Allen 2002-11-02 22:26 Bruce Allen 2002-11-02 8:26 Tim Prince 2002-11-02 7:46 Marco Bernardo 2002-10-31 0:56 Bruce Allen 2002-10-31 0:46 Marco Bernardo 2002-10-30 12:57 bangerth 2002-10-30 9:36 Bruce Allen 2002-10-30 0:26 bernardo
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=20021102155601.28368.qmail@sources.redhat.com \ --to=toon@moene.indiv.nluug.nl \ --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: linkBe 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).