Custom Query (1030 matches)

Given:

$ cat warning.lisp
xyz    ;;; e.g., a reference to a non-special free variable

;;; EOF
$

we can get:

? (compile-file "foo.lisp" :save-source-locations nil)
> Error: value NIL is not of the expected type NUMBER.
> While executing: --2, in process listener(1).
> Type :POP to abort, :R for a list of available restarts.
> Type :? for other options.

The error comes from code which tries to ensure that the COMPILER-WARNING will have an associated SOURCE-NOTE (presumably since if it didn't, the COMPILER-WARNING wouldn't have an associated SOURCE-NOTE ...) The SOURCE-NOTE's start-pos and end-pos are initialized to the value of *FCOMP-STREAM-POSITION*, which is NIL by the time this warning is signaled.

 (7FDCCEF42138) : 0 (--2 NIL NIL) 5245
 (7FDCCEF42170) : 1 (ENCODE-FILE-RANGE NIL NIL) 69
 (7FDCCEF42190) : 2 (MAKE-SOURCE-NOTE :FILENAME "home:warning.lisp.newest" :START-POS NIL :END-POS NIL :SOURCE NIL) 101
 (7FDCCEF421F8) : 3 (FCOMP-SIGNAL-OR-DEFER-WARNINGS (#<COMPILER-WARNING #x30200279B3ED>) #<LEXICAL-ENVIRONMENT #x30200279B67D>) 333
 (7FDCCEF42250) : 4 (FCOMP-NAMED-FUNCTION (LAMBDA NIL (PROGN XYZ)) NIL #<LEXICAL-ENVIRONMENT #x30200279CD9D> NIL) 597
 (7FDCCEF422C0) : 5 (FCOMP-COMPILE-TOPLEVEL-FORMS #<LEXICAL-ENVIRONMENT #x30200279CD9D>) 693

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.

Calling WARN messes with the pretty-printer.

CL-USER> (lisp-implementation-version)
"Version 1.4-RC1-r13031  (LinuxX8632)"
CL-USER> (setq *print-pretty* t)
T

CL-USER> (format t "~@<COMPILE-FILE failed while performing ~A on ~A.~@:>"
                 "#<COMPILE-OP (:FORCE T) #x150A26AE>" 
                 "#<IRONCLAD-SOURCE-FILE \"ripemd-160\" #x14D18B46>")
COMPILE-FILE failed while performing #<COMPILE-OP (:FORCE T) #x150A26AE> on
#<IRONCLAD-SOURCE-FILE "ripemd-160" #x14D18B46>.
NIL

CL-USER> (warn "~@<COMPILE-FILE failed while performing ~A on ~A.~@:>"
              "#<COMPILE-OP (:FORCE T) #x150A26AE>"
               "#<IRONCLAD-SOURCE-FILE \"ripemd-160\" #x14D18B46>")
; Warning: COMPILE-FILE failed while performing
;                     #<COMPILE-OP (:FORCE T) #x150A26AE> on
;                     #<IRONCLAD-SOURCE-FILE "ripemd-160" #x14D18B46>.
; While executing: SWANK::EVAL-REGION, in process repl-thread(11).
NIL

As you can see, WARN somehow messes with pretty-printing.