The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Luther Johnson <luther.johnson@makerlisp.com>
To: tuhs@tuhs.org
Subject: [TUHS] Re: 386 PCC
Date: Sat, 23 Mar 2024 17:25:24 -0700	[thread overview]
Message-ID: <28a2daa5-466b-0b79-d416-0e1bec179bca@makerlisp.com> (raw)
In-Reply-To: <257e33f8-1ab9-37a1-cd7b-072ed20b5528@makerlisp.com>

As PCC (original version, not 2.0 or any of the Research Unix versions
after) was the compiler for BSD right up through 4.3, maybe some of the
early 386 BSDs used PCC too.

On 03/23/2024 05:17 PM, Luther Johnson wrote:
> I think it's a better than even chance that the C compilers in the first
> versions of SCO and ISC Unix were based on PCC, you might look there.
>
> On 03/23/2024 05:13 PM, Jason Stevens 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!
>>
>>
>
>


  parent reply	other threads:[~2024-03-24  0:25 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 [this message]
2024-03-24  0:27     ` Charles H Sauer (he/him)
2024-03-24  2:00 ` segaloco via TUHS
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=28a2daa5-466b-0b79-d416-0e1bec179bca@makerlisp.com \
    --to=luther.johnson@makerlisp.com \
    --cc=tuhs@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
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).