[Openmcl-devel] ARM testing

David Brown lisp at davidb.org
Thu Jan 20 00:24:09 UTC 2011

Since my day job involves working on the Linux kernel on ARM targets, I
thought I'd give the new ARM CCL port a try.  It doesn't get very far,
and was wondering if anyone had any suggestions on what would be a good
way to investigate this.

The userspace is running Ubuntu 10.04, and I've built the kernel myself
(currently off of 2.6.37-rc6, soon 2.6.38-rc1).

The CPU is an ARM v7 (QSD8x50, same as what's in the Nexus One).

On running ./armcl, I get

Unhandled exception 4 at 0x508f4248, context->regs at #xbead82e0
wrong number of args (1) to #<Function (:INTERNAL SAVE-IMAGE)
? for help
[2430] Clozure CL kernel debugger: r
r00 = 0x00000013    r08 = 0xBEBCA628
r01 = 0x0000000A    r09 = 0x544363AE
r02 = 0x00000004    r10 = 0x403E0FFC
r03 = 0x000383D0    r11 = 0x00000000
r04 = 0x5455871E    r12 = 0xFFFFFFF8
r05 = 0x00000000    r13 = 0xBEBCA5B0
r06 = 0x00000000    r14 = 0x0001D7CC
r07 = 0x00000000    r15 = 0x508F4248
[2430] Clozure CL kernel debugger: v
Lisp kernel svn revision: 14487
Symbol *OPENMCL-VERSION* at #x541F09DE
  value    : "1.6-r14468M  (~A)"
[2430] Clozure CL kernel debugger: b
current thread: tcr = 0x383d0, native thread ID = 0x97e, interrupts

(#xBEBCA5D0) #x0001D7BC : (subprimitive toplevel_loop)
(#xBEBCA5E0) #x0001D84C : (subprimitive (null))
[2430] Clozure CL kernel debugger: t
Current Thread Context Record (tcr) = 0x383d0
Control (C) stack area:  low = 0xbea67000, high = 0xbebca628
Value (lisp) stack area: low = 0x403e1000, high = 0x40295000
Exception stack pointer = 0xbebca5b0
[2429] Clozure CL kernel debugger: k

Thanks for any ideas,

More information about the Openmcl-devel mailing list