The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: segaloco via TUHS <tuhs@tuhs.org>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: 386 PCC
Date: Sun, 24 Mar 2024 02:00:18 +0000	[thread overview]
Message-ID: <VZ8jYkq94RrjTD4EHEsyzz_h3mClaUMsR2Ph3dRcRyaibsJZaPmogwZ_d618xOB3xP8F9s_XDm9KgSMVgmvKZD5Ac8pq4y6sgrh5NqcBPsY=@protonmail.com> (raw)
In-Reply-To: <7D65B884BDE2EE11A8F800155D08821210B2@SGMCEXCH>

On Saturday, March 23rd, 2024 at 5:13 PM, Jason Stevens <jsteve@superglobalmegacorp.com> wrote:

> I'd been on this whole rabbithole exploration thing of those MIT PCC 8086
> uploads that have been on the site & on bitsavers, it had me wondering is
> there any version of PCC that targeted the 386?
>
> While rebuilding all the 8086 port stuff, and MIT PC/IP was fun, it'd be
> kind of interesting to see if anything that ancient could be forced to work
> with a DOS Extender..
>
> I know there was the Anders Magnusson one in 2007, although the site is now
> offline. But surely there must have been another one between 1988/2007?
>
> Thanks!

A cursory glance at the SVR4/386 SGS reveals some pcc fingerprints in the compiler bits at /usr/src/cmd/sgs/cg

For instance the machine-dependent bits are shunted off to files including local.c and local2.c, within these files exist similar entrypoints like lineid and zzzcode and arrays like rnames and ccbranches.  This is comparing with the version of pcc in V7.  I wasn't there so can't speak with authority but it does look like there is still pcc DNA as of SVR4/386.  Looking a bit further forward, this compiler seems to still be in use as of 1997's UnixWare aka "SVR5".

- Matt G.

  parent reply	other threads:[~2024-03-24  2:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-24  0:13 [TUHS] " Jason Stevens
2024-03-24  0:17 ` [TUHS] " Luther Johnson
2024-03-24  0:20   ` Charles H Sauer (he/him)
2024-03-24  2:34     ` Heinz Lycklama
2024-03-24  0:25   ` Luther Johnson
2024-03-24  0:27     ` Charles H Sauer (he/him)
2024-03-24  2:00 ` segaloco via TUHS [this message]
2024-03-25  8:46 ` arnold
2024-03-25  9:17 ` Angus Robinson
2024-03-25  9:07 Jason Stevens
2024-03-25  9:32 Jason Stevens

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='VZ8jYkq94RrjTD4EHEsyzz_h3mClaUMsR2Ph3dRcRyaibsJZaPmogwZ_d618xOB3xP8F9s_XDm9KgSMVgmvKZD5Ac8pq4y6sgrh5NqcBPsY=@protonmail.com' \
    --to=tuhs@tuhs.org \
    --cc=segaloco@protonmail.com \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).