In article <ma**********************************@python.org >, Tim Peters
<ti*****@comcast.net> writes
.......
Python itself assumes that no-stop mode is in effect (the IEEE-754 mandated
default: all FPU traps are disabled).
.....
That at least makes resetting easy when one can do it.
I guessed all Python floating point ops are tested either pre or post
for the correct outcome, but then I tried
a=1e290
a
1.0000000000000001e+290 a*a1.#INF
so I suppose only the obvious things are tested.
-it's hard being an fpu'ly yrs-
Robin Becker