Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!ucla-cs!zen!ucbvax!ji.Berkeley.EDU!woutput
From: woutput@ji.Berkeley.EDU (Andrew Purshottam)
Newsgroups: comp.lang.c
Subject: Re: Porting PCC
Message-ID: <19614@ucbvax.BERKELEY.EDU>
Date: Mon, 6-Jul-87 07:37:27 EDT
Article-I.D.: ucbvax.19614
Posted: Mon Jul  6 07:37:27 1987
Date-Received: Tue, 7-Jul-87 01:40:35 EDT
References: <2082@dg_rtp.UUCP>
Sender: usenet@ucbvax.BERKELEY.EDU
Reply-To: woutput@ji.Berkeley.EDU.UUCP (Andrew Purshottam)
Organization: University of California, Berkeley
Lines: 21
Keywords: pcc, cc, compiler, Sam Leffler
Summary: The refernce on porting pcc

The paper mention from case was by Sam Leffler, and
was called "A Detailed Tour through the /6 C Complier."
It's quite useful, if you are going to start with pcc1.
A Graham student also wrote a paper on the pcc1 IR.
It had a bell copyright warning, and I am not sure of its
status.

An adventurous alternative: consider using gcc, RMS's 
new C compiler now in beta release. It's free, though 
you can legally make proprietary subversions.
(I wonder at the enforcablity of this, though; if there
is one thing I have learned as a CS undergrad here,
it's been how to "continuously deform" one program into another,
with no trace of ancestry. Of course, none of us would ever 
do that :-)

Andy


    Cheers, Andy (...!ucbvax!woutput woutput@ji.berkeley.edu)
(cond ((lovep you (quote LISP)) (honk)) (t (return ())))