Home > Archive > Fortran > August 2005 > Re: Checking for IEEE Infinity
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Re: Checking for IEEE Infinity
|
|
| Kevin G. Rhoads 2005-08-15, 5:02 pm |
| >I am not sure that the blame is (entirely) on CVF. I have had the same
>sort of problems with a C program
AFAIK this is a problem with MS OSes where the MS C/C++ RTL will "smash" the
FPU settings. Each and every program developed with MS tools does this. Including
DLLs. Including system DLLs. And apparently the OS does not restore FPU state
*completely* during task swtiches.
Since this appears to be a deep-seated design flaw, getting useful information
from MS is problematic. Since this is an FPU issue, the alternative sources of
information appear to pay little attention. Since this is an MS issue, many
other sources of information completely ignore it, except occasionally to smirk.
The FPU settings issues also affects programs developed with older Borland tools,
since MS changed the default settings imposed by the RTL at one point. Borland
tools, expecting to be able to set and then forget FPU settings started having
problems with FPU settings were changed back to the new defaults randomly during
program execution (i.e., on some task switch which was supposed to be transparent
to the executing program). I think Borland changed the expectations of their RTL
to match the new MS default as a way to "cure" this.
| |
| Abdul Qat 2005-08-16, 4:01 am |
|
"Kevin G. Rhoads" <kgrhoads@alum.mit.edu> wrote in message
news:4300AB33.6A66CF42@alum.mit.edu...
>
> AFAIK this is a problem with MS OSes
[anti Microsoft diatribe elided].
There isn't one iota of truth in your post.
--
Salaam,
Abdul Q.
______
"Facts are meaningless. You could use facts to prove anything that's even
remotely true." -- Homer Simpson.
| |
| Kevin G. Rhoads 2005-08-16, 5:06 pm |
| >[anti Microsoft diatribe elided].
>
>There isn't one iota of truth in your post.
There was at least ONE iota of truth there ;-), and I refuse to be drawn
in to your nastiness. I don't claim to have it all right, but MS did start
changing the way the FPU was set at some point, way back when 16 bit dev tools
were still quite common. I had to deal with it then, I certainly don't claim
to have gotten it all then, let alone to remember it all now.
You on the other hand appear to be claiming omniscience, and too often fail.
So, flame on. Since you haven't bothered to provide any useful technical info,
flame on.
|
|
|
|
|