From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HTML_FONT_LOW_CONTRAST,HTML_MESSAGE,MAILING_LIST_MULTI, RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 30434 invoked from network); 25 Apr 2021 17:12:42 -0000 Received: from minnie.tuhs.org (45.79.103.53) by inbox.vuxu.org with ESMTPUTF8; 25 Apr 2021 17:12:42 -0000 Received: by minnie.tuhs.org (Postfix, from userid 112) id 4AFBB9C094; Mon, 26 Apr 2021 03:12:40 +1000 (AEST) Received: from minnie.tuhs.org (localhost [127.0.0.1]) by minnie.tuhs.org (Postfix) with ESMTP id DE9B09BD87; Mon, 26 Apr 2021 03:11:58 +1000 (AEST) Authentication-Results: minnie.tuhs.org; dkim=pass (1024-bit key; unprotected) header.d=ccc.com header.i=@ccc.com header.b="OQMApdGk"; dkim-atps=neutral Received: by minnie.tuhs.org (Postfix, from userid 112) id D808A9BD87; Mon, 26 Apr 2021 03:11:55 +1000 (AEST) Received: from mail-qv1-f49.google.com (mail-qv1-f49.google.com [209.85.219.49]) by minnie.tuhs.org (Postfix) with ESMTPS id 67BA79BD71 for ; Mon, 26 Apr 2021 03:11:52 +1000 (AEST) Received: by mail-qv1-f49.google.com with SMTP id ef17so20511825qvb.0 for ; Sun, 25 Apr 2021 10:11:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ccc.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ekXOkTO5V/LDy6CXS7If5Ga9EAzd4aC7wK6DvtNJy0w=; b=OQMApdGk2hxPO7svVgQW073RQQFr1bfsS1qj254pATuSrrfagDcipqB0n4tdRFUp42 ZOZu2pkEAy7bvWQQo7ZN+TWuwbjU4ll/bnkSb+8HhjkypWWkhdGFJX0iDgMHiKCd7k0l G499eTxUdS3nPzORM5q5zRJca255608uYp5YA= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ekXOkTO5V/LDy6CXS7If5Ga9EAzd4aC7wK6DvtNJy0w=; b=RlNZvkrwDJYQGs8Ps7Yo7SqBsszB+YyNEV46IgKoVF0D3bRNVqzWqfhWWDS4puxT4F nCmgIV8eD/NIwZ8+GnSTGVFolUuSYDEEQWUIQ650iv/xofayVkZPc1xUGPrzZTYR8laC n7tWxPn0BFWkIYEoKSHZOfw6dPS1Mwfw8/0SC6CDzI+qEno5qoB6py/6gTA/xlfxqUHG m0O1y2YAFZ5BPDSCuwiGm0rGGCYZU4XpXGBEh+NJCG8p88N9VtotK1ovvc7+ENShpCSl 6K5wSpX7/Eg5wVqdDzpo0TglzKEU/b3BPzWdgLYnxHh7K3TSBdieghKMvrwCCO1fZmU7 6G0w== X-Gm-Message-State: AOAM533/l60ky/UhQuIybNroH4rGaQ4Ylz2z1JpcSoXtBRB9NzPIaxbu qmyV/TkfZ2NICTRt0q640xzyOk4Zw9OH13tRIS8gYQo0wUc= X-Google-Smtp-Source: ABdhPJw+HfzlYQwFx6xCTv+vQ0tlt1T+owKrlL8xrNoM7GWu5bURq1alk34U+YMGOQSyQw2Uh0vl1OpTPzEJmaVPTD8= X-Received: by 2002:a0c:b303:: with SMTP id s3mr13962419qve.22.1619370711359; Sun, 25 Apr 2021 10:11:51 -0700 (PDT) MIME-Version: 1.0 References: <15D66A4F-D935-4313-93C8-CBB66039E0BD@planet.nl> <202104251249.13PCnaFV031741@freefriends.org> In-Reply-To: From: Clem Cole Date: Sun, 25 Apr 2021 13:11:25 -0400 Message-ID: To: Paul Ruizendaal Content-Type: multipart/alternative; boundary="00000000000002b85205c0cf20c7" Subject: Re: [TUHS] pcc in 8th edition X-BeenThere: tuhs@minnie.tuhs.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: The Unix Heritage Society mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: TUHS main list Errors-To: tuhs-bounces@minnie.tuhs.org Sender: "TUHS" --00000000000002b85205c0cf20c7 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable yes i'll mail under separate cover a scan =E1=90=A7 On Sun, Apr 25, 2021 at 11:47 AM Paul Ruizendaal 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 th= e > 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.=E2=80=9D > > 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 a= t > > git://github.com/arnoldrobbins/pcc-revived > > > > HTH, > > > > Arnold > > > > Paul Ruizendaal wrote: > > > >> For clarity and ease of reference: > >> > >> - The =E2=80=9CTour of paper=E2=80=9D is for instance here: > http://citeseerx.ist.psu.edu/viewdoc/summary?doi=3D10.1.1.48.3512 < > http://citeseerx.ist.psu.edu/viewdoc/summary?doi=3D10.1.1.48.3512> > >> > >> - A machine description for the VAX that matches with that paper is fo= r > instance in the SysIII source: > https://www.tuhs.org/cgi-bin/utree.pl?file=3DSysIII/usr/src/cmd/cc/vax/pc= c/table.c > < > https://www.tuhs.org/cgi-bin/utree.pl?file=3DSysIII/usr/src/cmd/cc/vax/pc= c/table.c > > > >> > >> - The new style description in 8th edition is here: > https://www.tuhs.org/cgi-bin/utree.pl?file=3DV8/usr/src/cmd/ccom/vax/stin= < > https://www.tuhs.org/cgi-bin/utree.pl?file=3DV8/usr/src/cmd/ccom/vax/stin= > > >> > >> - The program that translates the =E2=80=9Cstin=E2=80=9D file to a =E2= =80=9Ctable.c=E2=80=9D file is > here: > https://www.tuhs.org/cgi-bin/utree.pl?file=3DV8/usr/src/cmd/ccom/common/s= ty.y > < > https://www.tuhs.org/cgi-bin/utree.pl?file=3DV8/usr/src/cmd/ccom/common/s= ty.y > > > >> > >> > >> =3D=3D=3D=3D > >> > >> 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 th= e > 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 som= e > issues, so I started looking at the PCC source. > >> > >> This source does not have a =E2=80=9Ctable.c=E2=80=9D in the well know= n format as > described in the =E2=80=9CA tour of the portable C compiler=E2=80=9D pape= r. Instead it uses > a file =E2=80=9Cstin=E2=80=9D which appears to be in a more compact forma= t and is > translated into a =E2=80=9Ctable.c=E2=80=9D file by a new pre-processor (= "sty.y=E2=80=9D). Then > looking at the VAX compilers for 8th and 10th edition, these too use this > =E2=80=9Cstin=E2=80=9D 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 ST= Y > table and on how to use it? Any surviving reports or memos that would be > useful? > >> > >> Many thanks in advance > >> > >> Paul > >> > > --00000000000002b85205c0cf20c7 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
yes=C2=A0 i'll mail under separate=C2=A0cover a sca= n
=E1=90=A7

On Sun, Apr 25, 2021 at 11:47 AM Paul Ruize= ndaal <pnr@planet.nl> wrote:
=
By now found some m= ore 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 S= ummer 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".=C2=A0 It includes documentation of
stin file formats, PCC2 tree forms, debugging flags, and
compiler #defines.=C2=A0 The manual is expensive so it's worth it
most if you buy it before you figure it all out doing a
port.=C2=A0 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.=E2=80=9D

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.=C2=A0 It lives in CVS, but I have a git mi= rror at
> git://github.com/arnoldrobbins/pcc-revived
>
> HTH,
>
> Arnold
>
> Paul Ruizendaal <pnr@planet.nl> wrote:
>
>> For clarity and ease of reference:
>>
>> - The =E2=80=9CTour of paper=E2=80=9D is for instance here: http://citeseerx.ist.psu.edu/viewdoc/summ= ary?doi=3D10.1.1.48.3512 <ht= tp://citeseerx.ist.psu.edu/viewdoc/summary?doi=3D10.1.1.48.3512>
>>
>> - A machine description for the VAX that matches with that paper i= s for instance in the SysIII source: https://www.tuhs.org/cgi-bin/utree.pl?file=3DSysIII/usr/= src/cmd/cc/vax/pcc/table.c <https://www.tuhs.org/cgi-bin/utree.pl?file=3DSysIII/usr/sr= c/cmd/cc/vax/pcc/table.c>
>>
>> - The new style description in 8th edition is here: https://www.tuhs.org/cgi-bin/utree.pl?fil= e=3DV8/usr/src/cmd/ccom/vax/stin <https://www.tuhs.org/cgi-bin/utree.pl?file=3DV8/usr/src/cmd/c= com/vax/stin>
>>
>> - The program that translates the =E2=80=9Cstin=E2=80=9D file to a= =E2=80=9Ctable.c=E2=80=9D file is here: https://www.tuhs.org/cgi-bin/utree.pl?file=3DV8/usr/src/c= md/ccom/common/sty.y <https://www.tuhs.org/cgi-bin/utree.pl?file=3DV8/usr/src/cmd/ccom/comm= on/sty.y>
>>
>>
>> =3D=3D=3D=3D
>>
>> Sometimes one thing leads to another.
>>
>> Following the recent mention of some retro-brew 68K single board s= ystems, I decided to build a CB030 board (in progress). I figure it is a ro= ugh 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 wit= h the Blit sources (see THUS Archive for this), as I had used that before t= o 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 =E2=80=9Ctable.c=E2=80=9D in the well = known format as described in the =E2=80=9CA tour of the portable C compiler= =E2=80=9D paper. Instead it uses a file =E2=80=9Cstin=E2=80=9D which appear= s to be in a more compact format and is translated into a =E2=80=9Ctable.c= =E2=80=9D file by a new pre-processor ("sty.y=E2=80=9D). Then looking = at the VAX compilers for 8th and 10th edition, these too use this =E2=80=9C= stin=E2=80=9D 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 t= he STY format.
>>
>> Anybody on this list that can shed some light on the history of th= e STY table and on how to use it? Any surviving reports or memos that would= be useful?
>>
>> Many thanks in advance
>>
>> Paul
>>

--00000000000002b85205c0cf20c7--