Custom Query (1030 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (307 - 309 of 1030)

Ticket Resolution Summary Owner Reporter
#1186 fixed FORMAT prints one digit too many after decimal point for ~e directive Robert Dodier
Description

FORMAT prints one digit too many after decimal point for ~e directive (CLHS 22.3.3.2). E.g.:

$ ./lx86cl 
Welcome to Clozure Common Lisp Version 1.9-r16078  (LinuxX8632)!
? (loop for d in '(1 2 3 4 5 6) do (format t "~,ve ~,ve~%" d 1.2345678e-10 d 1.2345678e+10))
1.23E-10 1.23E+10
1.235E-10 1.235E+10
1.2346E-10 1.2346E+10
1.23457E-10 1.23457E+10
1.234568E-10 1.234568E+10
1.2345679E-10 1.2345678E+10
NIL

On the other hand SBCL 1.0.55.0 is correct from what I can tell:

* (loop for d in '(1 2 3 4 5 6) do (format t "~,ve ~,ve~%" d 1.2345678e-10 d 1.2345678e+10))
1.2e-10 1.2e+10
1.23e-10 1.23e+10
1.235e-10 1.235e+10
1.2346e-10 1.2346e+10
1.23457e-10 1.23457e+10
1.234568e-10 1.234568e+10
NIL
#1190 fixed CPU check fails on Raspberry Pi latest revision Mark Brown
Description

Attempting to use the ARM version of CCL 1.9 on a recent model Raspberry Pi (Linux 3.10.25+), armcl fails to start with the message: "CPU doesn't support required features"

Investigation shows that the check_arm_cpu function in pmcl_kernel.c is not correctly interpreting the output of /proc/cpuinfo. My Raspberry Pi shows the following:

$ cat /proc/cpuinfo
processor	: 0
model name	: ARMv6-compatible processor rev 7 (v6l)
BogoMIPS	: 2.00
Features	: swp half thumb fastmult vfp edsp java tls 
CPU implementer	: 0x41
CPU architecture: 7
CPU variant	: 0x0
CPU part	: 0xb76
CPU revision	: 7

Hardware	: BCM2708
Revision	: 000d
Serial		: ******************

check_arm_cpu looks for the string "Processor" (with an upper case P) at the start of each line, using strncmp. However, because the Raspberry Pi is returning "processor" (with a lower case p) the line is not recognised.

The fix is simply to change strncmp to strncasecmp.

There are other issues with the function as well, one being that calls are made to malloc() but the return value is not checked. These can be avoided by allocating procline and cpuline on the stack, with the same size as the input line buffer. This trades off wasting a maximum of 258 bytes of memory on the stack to avoid the overhead of calling malloc() and free() and having to check the return values from malloc().

A modified version of pmcl_kernel.c is included - the changes are to check_arm_cpu only. However, it has not been tested with anything except the Raspberry Pi in my possession.

#1192 fixed Bordeaux FFT problem Fred Bayer
Description

Are specialized arrays for complex numbers supposed to work, yet?

I tried loading bordeaux-fft on an Odroid U3 (linuxarm) and got this:

Welcome to Clozure Common Lisp Version 1.10-dev-r16104-trunk (LinuxARM32)!

? (ql:quickload "bordeaux-fft") To load "bordeaux-fft":

Load 1 ASDF system:

bordeaux-fft

; Loading "bordeaux-fft" [package bordeaux-fft]

Error: bad regspec: :COMPLEX-DOUBLE-FLOAT-VECTOR While executing: CCL::%HARD-REGSPEC-CLASS, in process listener(1). Type :POP to abort, :R for a list of available restarts. Type :? for other options.

The backtrace is attached.

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.