Rainer Schuetze <> changed:

           What    |Removed                     |Added
                 CC|                            |

--- Comment #3 from Rainer Schuetze <> 2012-10-02 11:16:06 
PDT ---
I haven't checked the disassembly, but I guess the problem of the failing
comparison is caused by storing one value to memory as double (and doing some
rounding on it along the way), while the other is still available on the FPU
stack with real-precision. You might get different results when enabling

The "is" comparison is a bitwise comparison, so it will probably actually write
both values to memory before the comparison, applying the same rounding to both

Configure issuemail:
------- You are receiving this mail because: -------

Reply via email to