Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu! ucbvax!ucsd!sdcsvax!trantor.harris-atd.com!trantor!mwills From: mwi...@x102a.harris-atd.com (wills ms 01309) Newsgroups: comp.sys.tahoe Subject: GCC & G++ Message-ID: <MWILLS.89Mar10122724@x102a.harris-atd.com> Date: 10 Mar 89 17:27:24 GMT Sender: n...@trantor.harris-atd.com Distribution: usa Organization: Harris Gov't Aerospace Systems Division Lines: 10 Posting-Front-End: GNU Emacs 18.47.1 of Thu Oct 15 1987 on x102a (hcx/ux) Has anyone brought up GNU C (GCC) and/or G++ on the tahoe? We're doing extensive C, Ada, and GNU lisp work on a Harris HCX-9 and I would like to know of others who are similarly involved!!! Please respond to this posting or via email or phone (407-729-3283). -- - Scott Wills mwi...@x102a.harris-atd.com uunet!x102a!mwills
Path: utzoo!attcan!uunet!ncrlnk!ncrcae!hubcap!gatech!bloom-beacon! tut.cis.ohio-state.edu!ucbvax!OKEEFFE.BERKELEY.EDU!bostic From: bos...@OKEEFFE.BERKELEY.EDU (Keith Bostic) Newsgroups: comp.sys.tahoe Subject: GCC & G++ Message-ID: <8903102008.AA08736@okeeffe.Berkeley.EDU> Date: 10 Mar 89 20:08:44 GMT Sender: dae...@ucbvax.BERKELEY.EDU Organization: The Internet Lines: 6 > Has anyone brought up GNU C (GCC) and/or G++ on the tahoe? Devon Bowen and some people at The University of New York at Buffalo have GCC running on the tahoe. His address is "bo...@cs.buffalo.edu". --keith
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu! ucbvax!hoptoad!gnu From: g...@hoptoad.uucp (John Gilmore) Newsgroups: comp.lang.lisp Subject: Porting Franz Lisp to run under Gnu C Message-ID: <7487@hoptoad.uucp> Date: 31 May 89 20:40:08 GMT References: <1196@cayman.cme.nbs.gov> Organization: Grasshopper Group in San Francisco Lines: 23 I have been working on making the whole BSD Unix system compile under gcc (the GNU C compiler). UCB intends to use gcc as "cc" in future BSD releases, though the old pcc compiler will still be around somewhere. One big stumbling block is Franz Lisp, which is rife with machine- and compiler-dependencies. Rather than replace these fragile dependencies with different fragile dependencies, I have been removing them, making the code more portable. After a few days' work, I have the Lisp interpreter compiling with gcc and pcc (and presumably any other C compiler). There are a few loose ends to smooth out but it's basically there. However, 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. 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? -- John Gilmore {sun,pacbell,uunet,pyramid,amdahl}!hoptoad!gnu g...@toad.com A well-regulated militia, being necessary to the security of a free State, the right of the people to keep and bear arms, shall not be infringed.