Custom Query (1030 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (853 - 855 of 1030)

Ticket Resolution Summary Owner Reporter
#29 worksforme Can't Finder open .Lisp files by dragging their icons to the Dock Gary Byers Andrew Shalit
Description

With the IDE running, I can open .lisp files from File/Open... menu. However, if I try to open them by dragging them from the Finder onto the IDE's icon in the dock, I get the message, "You cannot open the application "OpenMCL" because it is not supported on this architecture. I'm running on Intel/Leopard. Same thing happens for text files.

#642 invalid Call to WARN messes with pretty-printer Tobias C. Rittweiler
Description

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.

#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.

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