On 2/20/07, Joel Salomon <[EMAIL PROTECTED]> wrote:
My system doesn't seem to like it when I call NaN(2):
That is the default behavior. See getfcr(2). In particular,
if you add
setfcr(getfcr()&~FPINVAL);
to your program then you can carry NaNs around willy-nilly
without causing exceptions.
On 2/20/07, Joel Salomon <[EMAIL PROTECTED]> wrote:
> this might be an alignment problem. but that's a wild guess.
I think not:
acid: SP
0x00000044
This tells you that SP's "address" is 0x44. (The registers appear to
have memory addresses starting at 0 in acid.) If you want to find
out what SP is, you have to dereference it, as in *SP.
On 2/20/07, erik quanstrom <[EMAIL PROTECTED]> wrote:
after a bit of actual thought, i think that NaN
is supposed to generate a note. if you do catch
the note, the program should work fine.
This is true too, though setfcr will avoid the notes entirely.
Russ
