On 9 Oct 1997, Douglas Bates wrote:
>
> Another thing to try is explicitly setting the floating point control
> word to the IEEE standard. Some older versions of the C libraries set
> the floating point control word to a non-standard value. That can
> affect the production and detection of NaN'
"Dr. Daniel Mashao" <[EMAIL PROTECTED]> writes:
> I could never reproduce the problem on a smaller code. If I put just one
> extra printf() statement the problem disappears and appears elsewhere in
> the code. Here is the code
>
> #define SCALE 8192/* scale for fixed point represent
>
> On Wed, 8 Oct 1997, E.L. Meijer (Eric) wrote:
>
> > Dunno if I may call myself an expert, but something that would really
> > help in diagnosing the problem, is to try to reduce the code to a small
> > code snippet that produces the problem. It is hard to comment without
> > seeing any actua
On Wed, 8 Oct 1997, E.L. Meijer (Eric) wrote:
> Dunno if I may call myself an expert, but something that would really
> help in diagnosing the problem, is to try to reduce the code to a small
> code snippet that produces the problem. It is hard to comment without
> seeing any actual code. The si
>
> I have ported some code from Sparc to Intel. The code works fine except it
> prints NaNs for some floats that are not NaNs at all. One of my co-workers
> suggested I run the same code (of course compiled) on FreeBsd and see if
> the NaNs appear. The FreeBsd code does not produce the NaNs. I ha
I have ported some code from Sparc to Intel. The code works fine except it
prints NaNs for some floats that are not NaNs at all. One of my co-workers
suggested I run the same code (of course compiled) on FreeBsd and see if
the NaNs appear. The FreeBsd code does not produce the NaNs. I have
searched
6 matches
Mail list logo
