The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Clem cole <clemc@ccc.com>
To: Jason Stevens <jsteve@superglobalmegacorp.com>
Cc: tuhs@tuhs.org
Subject: Re: [TUHS] PCC for the i386
Date: Thu, 11 Jul 2019 09:30:44 -0700	[thread overview]
Message-ID: <610F6FCB-F24D-4788-953A-83E0E6456622@ccc.com> (raw)
In-Reply-To: <ADFDF14544A65F35.7e6e7ae7-83e1-47fa-9568-f5498506233e@mail.outlook.com>

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

By the time of 4.2 the switch from the  Ritchie and Johnson compilers at UCB had begun.  Remember the primary output of Rms at that point was emacs and gcc.    

CSRG wanted the different backends for C.   ThAts it.  Besides the vax, Rms had done 68000 and 386 back ends then.  

With the original system V, all of AT&T, Intel and IBM paid Interactive Systems Corp (aka ISC) to port the System V/Vax code to a 386 ps/2 and an Intel reference system that used an ISA bus.  This would be eventually released in source at the 386 port from AT&T.   As part of the contract summit supplied the compiler

I know the AT&T assembler with it’s backwards syntax from Intel was done before rms did his.  He was compatible with the summit assembler.  I don’t remember who’s 386 backend came out first.  I think is was the summit compiler but you needed a system v license which UCB did not have. 

Clem

Sent from my PDP-7 Running UNIX V0 expect things to be almost but not quite. 

> On Jul 11, 2019, at 8:50 AM, Jason Stevens <jsteve@superglobalmegacorp.com> wrote:
> 
> That would make sense.   I was able to find some info on PCC2 here
> 
> http://doc.cat-v.org/unix/unix-before-berkeley/
> 
> I'm guessing along with the adoption of emacs the csrg must have been further gnu synergy...  Or maybe PCC2 just wasn't available outside of the labs? 
> 
> Or maybe by '88 gcc was already usurping many of the c compilers of the era. 
> 
> 
> 
> 
> 
> On Thu, Jul 11, 2019 at 11:37 PM +0800, "Clem cole" <clemc@ccc.com> wrote:
> 
>> I believe the pcc/386 came out of Steve Johnson team at Summit with the PCC2 work.  
>> 
>> Sent from my PDP-7 Running UNIX V0 expect things to be almost but not quite. 
>> 
>>> On Jul 11, 2019, at 7:53 AM, Jason Stevens <jsteve@superglobalmegacorp.com> wrote:
>>> 
>>> Does anyone know where the 386 port from PCC came from?
>>>  
>>> While trying to build a Tahoe userland for the i386, it seems that everything was built with GCC…
>>> Was there a PCC for the i386 around ’88-90?  It seems after the rapid demise of the Tahoe/Harris
>>> HCX-9 that the non Vax/HCX-9 platforms had moved to GCC?
>>>  
>>> Also anyone know any good test software for LIBC?  I’ve been tracing through some
>>> strange issues rebuilding LIBC from Tahoe, where I had to include some bits from
>>> Reno to get diropen to actually work.  I would imagine there ought to have been some
>>> platform exercise code to make sure things were actually working instead of say
>>> building as much as you can, and playing rogue for a few hours to make sure
>>> its stable enough.

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

  reply	other threads:[~2019-07-11 16:31 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-11 14:53 Jason Stevens
2019-07-11 15:12 ` arnold
2019-07-11 15:37 ` Clem cole
2019-07-11 15:50   ` Jason Stevens
2019-07-11 16:30     ` Clem cole [this message]
2019-07-11 16:42       ` Richard Salz
2019-07-11 16:48       ` Warner Losh
2019-07-11 17:05         ` Clem Cole
2019-07-11 19:39           ` Charles H Sauer
2019-07-12  0:14             ` Clem Cole
2019-07-11 16:50       ` A. P. Garcia
2019-07-11 16:54         ` Clem Cole
2019-07-12  3:44         ` Michael Parson
2019-07-17  7:37         ` [TUHS] Old 386 Unix Versions, was: " emanuel stiebler
2019-07-17  8:10           ` arnold
2019-07-17  9:28             ` Arrigo Triulzi
2019-07-17 10:09               ` Jason Stevens
2019-07-17 10:42               ` emanuel stiebler
2019-07-17 15:40                 ` Adam Thornton
2019-07-17 18:01                   ` Clem Cole
2019-07-17 12:32               ` Ben Greenfield via TUHS
2019-07-17 12:50                 ` Dagobert Michelsen
2019-07-17 13:38                   ` Arrigo Triulzi
2019-07-17 14:41                 ` Clem Cole
2019-07-17 15:08                   ` Ben Greenfield via TUHS
2019-07-17 21:09                     ` Dagobert Michelsen
2019-07-18  8:56                       ` Arrigo Triulzi
2019-07-17 16:04                   ` William Pechter
2019-07-17 14:34               ` Clem Cole
2019-07-17 23:22                 ` Bakul Shah
2019-07-18  0:04                   ` Clem cole
2019-07-17 22:48               ` Chris Hanson
2019-07-18  8:39                 ` Wesley Parish
2019-07-17 14:15             ` Clem Cole
2019-07-17 15:11             ` Larry McVoy
2019-07-17 15:31               ` Warner Losh
2019-07-17 15:36               ` Jason Stevens
2019-07-17 16:56                 ` Larry McVoy
2019-07-24  1:04               ` Lyndon Nerenberg
2019-07-24  1:30                 ` Arthur Krewat
2019-07-24 21:53                 ` Kevin Bowling
2019-07-25 19:16                   ` Lyndon Nerenberg
2019-07-25 19:29                     ` [TUHS] AT&T 3b4000 (was Re: Old 386 Unix Versions) Kevin Bowling
2019-07-25 20:47                       ` Clem Cole
2019-07-26 18:18                         ` Seth J. Morabito
2019-07-26 19:24                           ` Clem Cole
2019-07-18  0:04           ` [TUHS] BSD/386 (was: Old 386 Unix Versions, was: Re: PCC for the i386) Greg 'groggy' Lehey
2019-07-18  0:16             ` Richard Salz
2019-07-18  1:08               ` Greg 'groggy' Lehey
2019-07-18 15:01             ` Chet Ramey

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=610F6FCB-F24D-4788-953A-83E0E6456622@ccc.com \
    --to=clemc@ccc.com \
    --cc=jsteve@superglobalmegacorp.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).