From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,3c92c6036be004b5,start
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 2002-12-11 05:31:50 PST
Path: 
 archiver1.google.com!news1.google.com!newsfeed.stanford.edu!logbridge.uoregon.edu!server3.netnews.ja.net!south.jnrs.ja.net!server2.netnews.ja.net!CAMPUS.UniversityofEssex.com
NNTP-Posting-Host: 155.245.41.213
Newsgroups: comp.lang.ada
Date: Wed, 11 Dec 2002 13:26:22 -0000
Message-ID: <3df73bcc.15483884@news.essex.ac.uk>
Sender: "Sangwine, Stephen J" <sjs@essex.ac.uk>
From: sjs@essex.ac.uk (Dr Steve Sangwine)
Subject: Floating-point problems with gcc 3.2
X-Newsreader: Forte Free Agent 1.21/32.243
Xref: archiver1.google.com comp.lang.ada:31682
Date: 2002-12-11T13:26:22+00:00
List-Id: <comp.lang.ada>

I have been trying out gcc 3.2 in order to link Fortran code with Ada
and I have encountered problems with floating point. Ada code that
works correctly with gnat 3.14p and 3.15p gives incorrect numeric
values when compiled with gcc 3.2. I'm using the mingw binaries of gcc
3.2 running on Windows 2000.

I have also seen problems with Fortran code giving incorrect
floating-point results. I seem to recall seeing somewhere something
about a known problem with the floating-point unit not being properly
initialised or reloaded on a context switch. Has anyone else hit this
problem?

Steve Sangwine