X-pop3-spooler: POP3MAIL 2.1.0 b 3 961213 -bs- Delivered-To: pcg AT goof DOT com Message-ID: <3510DDA6.4C010E27@pfh.research.philips.com> Date: Thu, 19 Mar 1998 09:56:06 +0100 From: Thomas Koehler Organization: Philips X-Mailer: Mozilla 3.01 (X11; I; Linux 2.0.32 i686) MIME-Version: 1.0 To: Marc Lehmann CC: beastium-list AT desk DOT nl Subject: Re: paranoia & extra precision [was -fno-float-store in pgcc] References: <35094C21 DOT 6B3F0566 AT pfh DOT research DOT philips DOT com> <19980314021923 DOT 32075 AT cerebro DOT laendle> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: Marc Lehmann Status: RO X-Status: A Content-Length: 996 Lines: 34 Marc Lehmann wrote: > > On Fri, Mar 13, 1998 at 04:09:21PM +0100, Thomas Koehler wrote: > > > so what is the difference between the behaviour of programs compiled > > with -ffloat-store compared to setting the FPU-rounding mode to double > > via __setfpucw? (except that the -ffloat-store variante is much slower). > > you can still program ansi c. I think you mean that I can program platform independent (which ansi c rule is violated if I use __setfpucw in my programs?) > > with setfpucw, you have to store the cw on almost every fpu operation. > gcc already does this for integer concersions (for other reasons). Interesting. If I set the fpucw on startup in main using __setfpucw (e.g. because I want to get SIGFPE's), is it ensured that the rest of the program is executed with this fpucw? -- Thomas Koehler Philips Research Laboratories Division Technical Systems Roentgenstrasse 24-26 D-22335 Hamburg Germany phone: +40/5078-2103 e-mail: T DOT Koehler AT PFH DOT Research DOT Philips DOT com