Custom Query (1030 matches)

See the attached test case.

It appears that the TF bit in the flags register is getting set sometimes when restoring the saved flags from tcr.unboxed0 in SPffcall.

I don't understand how that bit is getting set. I added code to see if the bit was set when doing the initial pushfl, and never saw it. Yet, somehow, tcr.unboxed0 will occasionally end up with the TF bit set, and then we get the 0x80000004 (single-step) exception from Windows after we restore the flags with popfl.

In ccl 1.6 (32-bit), we get

1> (atan #c(-1d-20 2d0))
#C(-1.5707963267948966D0 0.5493061443340549D0)

This is right, I think. However,

2> (atan #c(-0d0 2d0))
#C(1.5707963267948966D0 0.5493061443340549D0)

The spec says that on the imaginary axis above i, atan is continuous on Quadrant II. Since float-sign -0d0) -> -1d0, both answers should have the same sign for the realpart.

In ccl 1.6 (32-bit) we have

1 > (atanh #c(-2d0 -1d-20))
#C(-0.5493061443340549D0 -1.5707963267948966D0)

but

1 > (atanh #c(-2d0 -0d0))
#C(-0.5493061443340549D0 1.5707963267948966D0)

The spec says that for on the negative real axis less than -1, atanh is continuous with Quadrant III. Since (float-sign -0d0) -> -1d0, both answers should have the same signs and the imaginary part should be negative.