logo       

Re: CMUCL on Opterons??: msg#00063

lisp.cmucl.devel

Subject: Re: CMUCL on Opterons??

On Sat, Feb 21, 2004 at 01:03:05AM +0000, Daniel Barlow wrote:
> Martin Cracauer <cracauer@xxxxxxxx> writes:
>
> > This doesn't work. The modes are not compatible enough to run a
> > literal piece of 32 bit binary code in a 64 bit process.
>
> What he says. In my (ongoing) SBCL port to the AMD64 I've run into
> two places so far where the x86 code generated by Python does
> something utterly different on x86-64 -
>

In case anyone is interested, the following is the status of my port
of CMUCL to AMD64. It ran many initialization functions and stopped in
the middle of type-init.lisp

Cheuksan Wang

amd64/lisp> gdb lisp
GNU gdb 5.3
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "x86_64-suse-linux"...
(gdb) r -core kernel.core
Keeping /home/wang/cmucl/amd64/lisp/lisp...
Starting program: /home/wang/cmucl/amd64/lisp/lisp -core kernel.core
In initial-function, and running.
GLOBALDB-INIT
FDEFN-INIT
TYPEDEF-INIT
CLASS-INIT
TYPE-INIT
Calling top-level forms.

Program received signal SIGTRAP, Trace/breakpoint trap.
0x0000000048332b50 in ?? ()
(gdb)





<Prev in Thread] Current Thread [Next in Thread>
Google Custom Search

News | FAQ | advertise