Re: Floating-point problems with gcc 3.2

["nicolas" <n.brunot@cadwin.com>]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1418 bytes --]

Gnat in gcc 3.1 and 3.2 is known to be very unstable.
Its main purpose seems to be good enough to be able to build higher versions
of Gnat

the situation is much better in 3.3 (but still expect more bugs than in Gnat
3.15p)
I would forget to use 3.1 or 3.2 for other purpose than building 3.3

You can wait for 3.3 version or try the experimental Gnat 3.3
http://prdownloads.sf.net/mingw/gnatgcc-3.3-exp-20021006.tar.gz
http://prdownloads.sf.net/mingw/gnatgcc-3.3-exp-20021006-notes.txt.gz

You can also try to build 3.3 yourself, but it is not so easy, especially
because mingw32 support is poor in the official FSF tree, and source files
have to be patched for this platform


"Dr Steve Sangwine" <sjs@essex.ac.uk> a �crit dans le message de news:
3df73bcc.15483884@news.essex.ac.uk...
> 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
>