| commit | 9585846595949e36ffc0090ec42444987f1f6c20 | |
| author | Christophe Rhodes <csr21@cam.ac.uk> | |
| Thu, 10 Jun 2004 13:33:18 +0000 (10 13:33 +0000) | ||
| committer | Christophe Rhodes <csr21@cam.ac.uk> | |
| Thu, 10 Jun 2004 13:33:18 +0000 (10 13:33 +0000) | ||
| tree | 8e8cfaf3c93799d5533cc4dfc7655ad44c7553a7 | treesnapshot (tar.gz zip) |
| parent | 3a618201c9f2370bb8784217a866d000371769e5 | commitdiff |
0.8.11.5:
Storing a floating point control word on the stack, then calling
out to C, is not guaranteed to behave when the called function
is likely to be messing around with the stack (purify() in
particular).
... reload the floating point control word before setting the
precision. This differs slightly in semantics from
before: changes caused by the C code will be propagated
to Lisp
Storing a floating point control word on the stack, then calling
out to C, is not guaranteed to behave when the called function
is likely to be messing around with the stack (purify() in
particular).
... reload the floating point control word before setting the
precision. This differs slightly in semantics from
before: changes caused by the C code will be propagated
to Lisp
| src/compiler/x86/c-call.lisp | diffblobblamehistory | |
| version.lisp-expr | diffblobblamehistory |