Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!uunet!mcvax!ukc!etive!aiai!jeff
From: jeff@aiai.ed.ac.uk (Jeff Dalton)
Newsgroups: comp.lang.lisp
Subject: Re: Porting Franz Lisp to run under Gnu C
Message-ID: <517@skye.ed.ac.uk>
Date: 2 Jun 89 12:50:47 GMT
References: <1196@cayman.cme.nbs.gov> <7487@hoptoad.uucp>
Reply-To: jeff@aiai.UUCP (Jeff Dalton)
Organization: AIAI, University of Edinburgh, Scotland
Lines: 24

In article <7487@hoptoad.uucp> gnu@hoptoad.uucp (John Gilmore) writes:
>the Lisp compiler is another matter; it seems to have lots more buried
>assumptions about how various C language "global variables" (the stack
>pointers) have magically been put into global machine registers.

Is this true for every target machine?  I know that the VAX version
assumes that, but I'm pretty sure the 68k one doesn't.  Indeed, I think
it has a switch that lets you say whether C register hacks have been
applied or not.

How many different machine architectures have to be supported these
days?  Is it supposed to work on the Tahoe?

>It looks like this is turning into a bigger effort than I and Berkeley
>can support.  Two questions:  Does anyone care if Franz Lisp moves into
>/usr/old and is desupported in BSD releases?  And, is there anyone who
>wants to take on the Lisp compiler conversion themselves?

I guess I would like to see Franz supported, but I don't think it's
so important now as it was in the past.

Jeff Dalton,                      JANET: J.Dalton@uk.ac.ed             
AI Applications Institute,        ARPA:  J.Dalton%uk.ac.ed@nsfnet-relay.ac.uk
Edinburgh University.             UUCP:  ...!ukc!ed.ac.uk!J.Dalton