The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Clem Cole <clemc@ccc.com>
To: Aharon Robbins <arnold@skeeve.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>, Paul Ruizendaal <pnr@planet.nl>
Subject: Re: [TUHS] pcc in 8th edition
Date: Sun, 25 Apr 2021 13:46:31 -0400
Message-ID: <CAC20D2Pa8ibh0gWPgMteoFhSC=J+BbuiU2vHAiYRs-ohF1y44A@mail.gmail.com> (raw)
In-Reply-To: <202104251732.13PHWb3o006219@freefriends.org>

[-- Attachment #1: Type: text/plain, Size: 4930 bytes --]

No worries, I already did -- but I also sent it back to the pubs' folks at
USENIX.  They have slowing scanning the print archives on an as-needed
basis; which is where it belongs.
ᐧ

On Sun, Apr 25, 2021 at 1:32 PM <arnold@skeeve.com> wrote:

> And maybe give to Warren too? :-)
>
> Clem Cole <clemc@ccc.com> wrote:
>
> > yes  i'll mail under separate cover a scan
> > ᐧ
> >
> > On Sun, Apr 25, 2021 at 11:47 AM Paul Ruizendaal <pnr@planet.nl> wrote:
> >
> > > By now found some more clues, in particular this link:
> > >
> http://computer-programming-forum.com/47-c-language/fab825b2dce1aa59.htm
> > >
> > > Apparently I am talking about PCC and PCC2 in the below question.
> > >
> > > The first post mentions 4 papers. They can be found online, apart from
> the
> > > USENIX one:
> > > "Four Generations of Portable C Compiler" by D.M. Kristol (1986 Summer
> > > USENIX Conference Proceedings)
> > >
> > > Anybody have that?
> > >
> > > The second post mentions official documentation:
> > >
> > > "In porting QCC, a useful text is the "Portable C Compiler -
> > > Version 2 (PCC2) Internals".  It includes documentation of
> > > stin file formats, PCC2 tree forms, debugging flags, and
> > > compiler #defines.  The manual is expensive so it's worth it
> > > most if you buy it before you figure it all out doing a
> > > port.  Since the manual is based on PCC2 (and hasn't been
> > > updated), it's a good starting point, but doesn't have the
> > > latest information.”
> > >
> > > Anybody have that? (It is not on bitsavers)
> > >
> > > Paul
> > >
> > > > On 25 Apr 2021, at 14:49, arnold@skeeve.com wrote:
> > > >
> > > > Not an answer to your questions, but you may want to take a look
> > > > at the PCC Revived project.  It lives in CVS, but I have a git
> mirror at
> > > > git://github.com/arnoldrobbins/pcc-revived
> > > >
> > > > HTH,
> > > >
> > > > Arnold
> > > >
> > > > Paul Ruizendaal <pnr@planet.nl> wrote:
> > > >
> > > >> For clarity and ease of reference:
> > > >>
> > > >> - The “Tour of paper” is for instance here:
> > > http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.48.3512 <
> > > http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.48.3512>
> > > >>
> > > >> - A machine description for the VAX that matches with that paper is
> for
> > > instance in the SysIII source:
> > >
> https://www.tuhs.org/cgi-bin/utree.pl?file=SysIII/usr/src/cmd/cc/vax/pcc/table.c
> > > <
> > >
> https://www.tuhs.org/cgi-bin/utree.pl?file=SysIII/usr/src/cmd/cc/vax/pcc/table.c
> > > >
> > > >>
> > > >> - The new style description in 8th edition is here:
> > >
> https://www.tuhs.org/cgi-bin/utree.pl?file=V8/usr/src/cmd/ccom/vax/stin <
> > >
> https://www.tuhs.org/cgi-bin/utree.pl?file=V8/usr/src/cmd/ccom/vax/stin>
> > > >>
> > > >> - The program that translates the “stin” file to a “table.c” file is
> > > here:
> > >
> https://www.tuhs.org/cgi-bin/utree.pl?file=V8/usr/src/cmd/ccom/common/sty.y
> > > <
> > >
> https://www.tuhs.org/cgi-bin/utree.pl?file=V8/usr/src/cmd/ccom/common/sty.y
> > > >
> > > >>
> > > >>
> > > >> ====
> > > >>
> > > >> Sometimes one thing leads to another.
> > > >>
> > > >> Following the recent mention of some retro-brew 68K single board
> > > systems, I decided to build a CB030 board (in progress). I figure it
> is a
> > > rough proxy for a 1980 VAX and would allow for some experimentation
> with
> > > the 32V / SysIII / 8th edition code.
> > > >>
> > > >> My first thought was to use the M68K compiler that is included with
> the
> > > Blit sources (see THUS Archive for this), as I had used that before to
> > > explore some of the Blit source. That compiler is LP32, not ILP32 -
> which
> > > may be a source of trouble. Just changing the SZINT parameter yielded
> some
> > > issues, so I started looking at the PCC source.
> > > >>
> > > >> This source does not have a “table.c” in the well known format as
> > > described in the “A tour of the portable C compiler” paper. Instead it
> uses
> > > a file “stin” which appears to be in a more compact format and is
> > > translated into a “table.c” file by a new pre-processor ("sty.y”). Then
> > > looking at the VAX compilers for 8th and 10th edition, these too use
> this
> > > “stin” file.
> > > >>
> > > >> All the other m68K compilers (based on pcc) that I found appear to
> > > derive from the V7/32V/SysIII lineage, not from the 8th edition
> lineage.
> > > >>
> > > >> A quick google did not yield much background or documentation on the
> > > STY format.
> > > >>
> > > >> Anybody on this list that can shed some light on the history of the
> STY
> > > table and on how to use it? Any surviving reports or memos that would
> be
> > > useful?
> > > >>
> > > >> Many thanks in advance
> > > >>
> > > >> Paul
> > > >>
> > >
> > >
>

[-- Attachment #2: Type: text/html, Size: 8070 bytes --]

  reply	other threads:[~2021-04-25 17:47 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-25 12:35 Paul Ruizendaal
2021-04-25 12:49 ` arnold
2021-04-25 14:04   ` Paul Ruizendaal
2021-04-25 15:45   ` Paul Ruizendaal
2021-04-25 17:11     ` Clem Cole
2021-04-25 17:32       ` arnold
2021-04-25 17:46         ` Clem Cole [this message]
2021-04-25 20:11       ` Paul Ruizendaal
2021-04-30 23:08       ` Paul Ruizendaal
  -- strict thread matches above, loose matches on Subject: below --
2021-04-26 18:00 Norman Wilson
2021-04-26 18:11 ` Dan Cross
2021-04-25 22:02 Norman Wilson
2021-04-26  0:18 ` Nemo Nusquam
2021-04-26 16:51 ` Adam Thornton
2021-04-25 20:48 Norman Wilson
2021-04-25 20:54 ` Dan Cross
2021-04-26  6:29 ` Noel Hunt
2021-04-25  9:15 Paul Ruizendaal via TUHS

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAC20D2Pa8ibh0gWPgMteoFhSC=J+BbuiU2vHAiYRs-ohF1y44A@mail.gmail.com' \
    --to=clemc@ccc.com \
    --cc=arnold@skeeve.com \
    --cc=pnr@planet.nl \
    --cc=tuhs@minnie.tuhs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

The Unix Heritage Society mailing list

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://inbox.vuxu.org/tuhs

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V1 tuhs tuhs/ http://inbox.vuxu.org/tuhs \
		tuhs@minnie.tuhs.org
	public-inbox-index tuhs

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.vuxu.org/vuxu.archive.tuhs


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git