Custom Query (1030 matches)

The log below shows an incorrect evaluation result.

I've marked this as "critical", but perhaps it should be "blocker". ACL2 relies on such multiplication being correct for its own checksum computations. We are hoping to release a new version of ACL2 this week.

Welcome to Clozure Common Lisp Version 1.10-dev-r16148M-trunk  (LinuxX8664)!
? (defun foo (u v)
    (declare (type fixnum u v))
    (* u v))
FOO
? most-positive-fixnum
1152921504606846975
? (foo 100000000000 100000000000)
-441130959790669824
? 

decode-float seems to be broken, it returns some random 3rd value instead of the sign:

[LinuxArm32, Odroid U3] Welcome to Clozure Common Lisp Version 1.10-dev-r16155M-trunk (LinuxARM32)!

? (decode-float pi) 0.7853981633974483D0 2 6.441148769597133D-232

Similarly on Windows X86 32Bit:

Welcome to Clozure Common Lisp Version 1.10-dev-r16103-trunk (WindowsX8632)!

? (decode-float pi) 0.7853981633974483D0 2 59757440

Windows X86 64Bit works ok:

Welcome to Clozure Common Lisp Version 1.10-dev (WindowsX8664)!

? (decode-float pi) 0.7853981633974483D0 2 1.0D0

Same behavior with single-floats.

When *print-circle* is T, FORMAT uses three times as much memory when printing conses compared to 1.9-r15757 (LinuxX8664), for example:

(defun test () (dotimes (k 100000) (format () "~a" '((a) (b)))))
(time (test))

Runtime is also increased, by ca. 25%

When *print-circle* is nil, the increase in memory usage is even bigger (almost tenfold).