From: Charles H Sauer <sauer@technologists.com>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] PCC for the i386
Date: Thu, 11 Jul 2019 14:39:48 -0500 [thread overview]
Message-ID: <bb93a96b-4c05-7036-0540-95e1ae596f96@technologists.com> (raw)
In-Reply-To: <CAC20D2MQ-castDpjCzJvKc5po322AQTF8g=2zgumdfywta8z+Q@mail.gmail.com>
Dell SVR4 included both pcc & gcc. gcc was used to build the system.
I think Richard Wirt's group at Intel contributed to optimization for
486, IIRC, probably for gcc, possibly for pcc.
I assume AIX/386 used pcc, but Clem likely knows for sure.
Charlie
On 7/11/2019 12:05 PM, Clem Cole wrote:
> Yup, that was Steve Ward's folks in the MIT/RTS group - it was the NU
> computer work. John Siber did most of the compiler work (funny, Steve
> Johnson and I were talking about some of that work last night at the
> UNIX50 party last night). tjt wrote the 68K assembler ward's folks
> used. I don't remember where the Z8000 assembler came, but I'm petty
> sure that the Intel assembler and some of the tools other John had
> brought back from his summers in MH.
>
> I think (but don't know for sure) the Intel 8086 assembler was done at
> AT&T first. IIRC it may have come out of Dale's group in Columbus. I
> do know Dale's group had done a Z80 C Compiler using the Ritchie
> Compiler at some point in 1978 timeframe (and at one time I had, but can
> not seem to find it, in my archives).
>
> When Intel released the 386, I believe the AT&T 8086 assembler was
> updated for the new 32 instructions; although who did that/where was
> done, I'm not sure.
>
> Steve is probably the best source for most of this as he managed the
> team in Summit doing the different AT&T front and back ends when they
> tried to centralize the compiler work for UNIX.
>
> On Thu, Jul 11, 2019 at 12:48 PM Warner Losh <imp@bsdimp.com
> <mailto:imp@bsdimp.com>> wrote:
>
>
>
> On Thu, Jul 11, 2019 at 10:31 AM Clem cole <clemc@ccc.com
> <mailto:clemc@ccc.com>> wrote:
>
> 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.
>
>
> There's also a fair amount of work at MIT to do Intel code
> generation for 8086 (small mode) that was extended by Queens College
> London (I think, I gotta grab the tapes again) to do large mode.
> I've run into this looking for a compiler for the Venix source
> restoration project I've been tilting at. I found those based on a
> cryptic comment I found somewhere online about the tech behind Venix
> that wasn't from AT&T. I don't know if ISC started with them as a
> base or not, nor really how the MIT compilers came about, but they
> claim to be PCC based somehow. Don't know if this helps you on your
> quest... BTW, I found these when I found the latest pcc-restoration
> sources didn't have a working i86 backend anymore (there was once
> one for Minux, but when I built it I couldn't get it to generate
> sensible code at all).
>
> Warner
>
> 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
> <mailto: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 <mailto: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
>> <mailto: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.
>>>
--
voice: +1.512.784.7526 e-mail: sauer@technologists.com
fax: +1.512.346.5240 Web: https://technologists.com/sauer/
Facebook/Google/Skype/Twitter: CharlesHSauer
next prev parent reply other threads:[~2019-07-11 19:40 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
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 [this message]
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=bb93a96b-4c05-7036-0540-95e1ae596f96@technologists.com \
--to=sauer@technologists.com \
--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
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).