Newsgroups: comp.lang.lisp,comp.sys.next.programmer
Path: cantaloupe.srv.cs.cmu.edu!das-news2.harvard.edu!news2.near.net!howland.reston.ans.net!ix.netcom.com!netcom.com!vrotney
From: vrotney@netcom.com (William Paul Vrotney)
Subject: Re: Porting cmu-cl to NeXT
In-Reply-To: sef@CS.CMU.EDU's message of 31 Jan 1995 05:12:57 GMT
Message-ID: <vrotneyD3AzEF.B8v@netcom.com>
Organization: NETCOM On-line Communication Services (408 261-4700 guest)
References: <3gk8dd$hrv@celebrian.otago.ac.nz> <3gkgsp$4al@cantaloupe.srv.cs.cmu.edu>
Date: Wed, 1 Feb 1995 04:06:15 GMT
Lines: 31
Xref: glinda.oz.cs.cmu.edu comp.lang.lisp:16594 comp.sys.next.programmer:22031

In article <3gkgsp$4al@cantaloupe.srv.cs.cmu.edu> sef@CS.CMU.EDU (Scott Fahlman) writes:

> In article <3gk8dd$hrv@celebrian.otago.ac.nz> brendon@black_albatross.otago.ac.nz (Brendon) writes:
> 
>    Has anyone attempted a port of cmu-cl to the NeXT yet? Currently
>    I am running CLISP and GCL which work O.K. but there are real
>    speed problems when compiling LARGE programs.
> 
> I'm pretty sure that nobody has seriously attempted a CMUCL port to
> the 68K architecture.  It would be a big job, and at this point a
> Great Leap Backward.
> 
> -- Scott
> 

Before NeXT decided to go software only I was analyzing CMUCL with the
intent of porting to NeXT 68k.  Around that time I believe that CMUCL was
ported to Intel 486 (correct me if I am wrong).  If this is so, a port to
NeXT on a 486 should not be too bad.

If someone with a NeXT 486 would like to try this I could point you to the
archives and code modules.  If this works out I might consider reopening the
68k port.

Also note that I posted a patch to allow Allegro CL 3.1.20 to run under NS
3.x 68k.


-- 

William P. Vrotney - vrotney@netcom.com
