Custom Query (1030 matches)
Results (313 - 315 of 1030)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1238 | fixed | x86 assembler gets operand order wrong on MOVQ between two XMM registers | ||
| Description |
? (ccl::defx86lapfunction bug ()
(movq (% fp1) (% fp0))
(ret))
BUG
? (disassemble *)
L0
(leaq (@ (:^ L0) (% rip)) (% fn)) ; [0]
(movq (% fp0) (% fp1)) ; [7]
(retq) ; [11]
NIL
DISASSEMBLE is correct in this case. |
|||
| #1241 | fixed | Apparent bug causes data mangling | ||
| Description |
https://lists.clozure.com/pipermail/openmcl-devel/2014-November/010720.html |
|||
| #1247 | fixed | socket timeout confusion | ||
| Description |
MAKE-SOCKET accepts timeout keyword arguments (:INPUT-TIMEOUT, :OUTPUT-TIMEOUT, and :CONNECT-TIMEOUT); non-null values of these arguments are supposed to be nonnegative REALs (according to the documentation) specifying time in seconds. ( Lower-level code (PROCESS-INPUT-WAIT, PROCESS-OUPUT-WAIT) takes optional timeout arguments which are required to be integers specifying time in milliseconds. MAKE-SOCKET seems to just pass its timeout arguments unmodified to the lower-level code. Wackiness ensues (in the formm of type-errors). See ticket:1242. I don't know whether this bug was newly introduced or if it's been present for a long time. |
|||
