From: Dave Love <d.love@dl.ac.uk>
To: egcs@cygnus.com
Subject: Re: FWD: FLOATING-POINT CONSISTENCY, -FFLOAT-STORE, AND X86
Date: Thu, 17 Dec 1998 11:20:00 -0000 [thread overview]
Message-ID: <rzqzp8mefsi.fsf@djlvig.dl.ac.uk> (raw)
In-Reply-To: <36781989.F5E61045@moene.indiv.nluug.nl>
>>>>> "Toon" == Toon Moene <toon@moene.indiv.nluug.nl> writes:
Toon> However, what I'm challenging is that we should burden
Toon> the compiler with these considerations *by default*
Indeed.
I haven't followed all this, but am somewhat bemused by it.
There are frequent complaints about Fortran due to the x86 register
business. All the ones I've checked have been covered by the advice
in the g77 manual to link code frobbing the control word (which allows
us to pass paranoia). Anyone know of exceptions?
[I started on implementing (as far as possible in f77-ish) the
Fortran2000 intrinsics for IEEE floating point control but gave up in
the absence of time to figure out more about the architectures which I
didn't have a clear story on. At some stage I hope to find time to
consult Reid (the author) and do what he says.]
next prev parent reply other threads:[~1998-12-17 11:20 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-12-16 13:52 Toon Moene
1998-12-17 10:06 ` Craig Burley
1998-12-17 12:16 ` Harvey J. Stein
1998-12-19 0:29 ` Craig Burley
1998-12-17 11:20 ` Dave Love [this message]
-- strict thread matches above, loose matches on Subject: below --
1998-12-17 14:38 Toon Moene
1998-12-17 15:30 ` Harvey J. Stein
1998-12-18 1:54 ` Toon Moene
1998-12-18 3:05 ` Harvey J. Stein
1998-12-18 9:01 ` Toon Moene
1998-12-18 15:59 ` Richard Henderson
1998-12-18 13:26 ` Marc Lehmann
1998-12-18 12:50 ` Dave Love
1998-12-17 14:37 tprince
1998-12-17 15:15 ` Stephen L Moshier
1998-12-17 11:27 Brad Lucier
1998-12-17 14:51 ` Marc Lehmann
1998-12-19 0:17 ` Craig Burley
1998-12-19 6:42 ` Emil Hallin
1998-12-19 14:26 ` Dave Love
1998-12-15 12:24 Toon Moene
1998-12-15 12:55 ` Joe Buck
1998-12-15 15:05 ` Edward Jason Riedy
1998-12-16 10:05 ` Craig Burley
1998-12-15 12:10 Geert Bosch
1998-12-15 13:09 ` Jeffrey A Law
1998-12-15 1:45 Geert Bosch
1998-12-15 3:34 ` Harvey J. Stein
1998-12-16 10:36 ` Craig Burley
1998-12-16 12:47 ` Harvey J. Stein
1998-12-17 10:22 ` Craig Burley
1998-12-17 14:54 ` Marc Lehmann
1998-12-19 0:27 ` Craig Burley
1998-12-19 5:06 ` Stephen L Moshier
1998-12-15 6:43 ` Stephen L Moshier
1998-12-16 10:14 ` Craig Burley
1998-12-15 9:29 ` Joe Buck
1998-12-15 10:14 ` Jeffrey A Law
1998-12-16 8:32 ` Sylvain Pion
1998-12-16 9:20 ` Craig Burley
1998-12-13 18:23 Stephen L Moshier
1998-12-14 1:52 ` Harvey J. Stein
1998-12-14 14:56 ` Edward Jason Riedy
1998-12-14 17:20 ` Joe Buck
1998-12-14 18:51 ` Edward Jason Riedy
1998-12-14 21:54 ` Craig Burley
1998-12-15 14:31 ` Edward Jason Riedy
1998-12-15 17:11 ` Jamie Lokier
1998-12-16 0:26 ` Harvey J. Stein
1998-12-16 9:33 ` Craig Burley
1998-12-16 12:18 ` Harvey J. Stein
1998-12-16 9:38 ` Craig Burley
1998-12-16 12:25 ` Marc Lehmann
1998-12-16 12:50 ` Tim Hollebeek
1998-12-16 13:04 ` Harvey J. Stein
1998-12-16 14:01 ` Marc Lehmann
1998-12-17 11:26 ` Dave Love
1998-12-17 15:06 ` Marc Lehmann
1998-12-18 12:50 ` Dave Love
1998-12-19 14:09 ` Marc Lehmann
1998-12-20 11:28 ` Dave Love
1998-12-20 11:24 ` Dave Love
1998-12-16 23:11 ` Joern Rennecke
1998-12-17 6:07 ` Jamie Lokier
1998-12-14 22:54 ` Craig Burley
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=rzqzp8mefsi.fsf@djlvig.dl.ac.uk \
--to=d.love@dl.ac.uk \
--cc=egcs@cygnus.com \
/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).