From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) 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,HEADER_FROM_DIFFERENT_DOMAINS,HTML_MESSAGE, MAILING_LIST_MULTI,MIME_QP_LONG_LINE,RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.2 Received: from minnie.tuhs.org (minnie.tuhs.org [45.79.103.53]) by inbox.vuxu.org (OpenSMTPD) with ESMTP id f134c754 for ; Thu, 11 Jul 2019 16:31:15 +0000 (UTC) Received: by minnie.tuhs.org (Postfix, from userid 112) id BE5AF94BE3; Fri, 12 Jul 2019 02:31:14 +1000 (AEST) Received: from minnie.tuhs.org (localhost [127.0.0.1]) by minnie.tuhs.org (Postfix) with ESMTP id EBD209480A; Fri, 12 Jul 2019 02:30:49 +1000 (AEST) Authentication-Results: minnie.tuhs.org; dkim=pass (1024-bit key; unprotected) header.d=ccc.com header.i=@ccc.com header.b="dzdEKxdP"; dkim-atps=neutral Received: by minnie.tuhs.org (Postfix, from userid 112) id 542569480A; Fri, 12 Jul 2019 02:30:48 +1000 (AEST) Received: from mail-pl1-f196.google.com (mail-pl1-f196.google.com [209.85.214.196]) by minnie.tuhs.org (Postfix) with ESMTPS id B3A57947D8 for ; Fri, 12 Jul 2019 02:30:47 +1000 (AEST) Received: by mail-pl1-f196.google.com with SMTP id y8so3285386plr.12 for ; Thu, 11 Jul 2019 09:30:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ccc.com; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=F+EZH+b/5mopHeRsH+vJYRJ4jASaRVURQn/S7S0N3mM=; b=dzdEKxdPQJvWbLahkUsz7ZyoLusjDivZ5O7QZdRiZtggr1hsJGzlAxmwc3tAbbfAX+ afeNQwqXlaJlpeAmD0Y5M2IYsmcMZHHbmim4RuC9EMdLYsL5oY5+ixdIbVG4x0YwHWF0 HM5Pfak3YmBlj1grZoQCgo5RqXPUbi9oiiujo= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=F+EZH+b/5mopHeRsH+vJYRJ4jASaRVURQn/S7S0N3mM=; b=HPEXJ2n05+1hRdk+Pd7QqJIt/9K/tC5qccNflOcmFt38UWQFXokY0ZTGqrb6+d+RR1 TERAY4p9/jZSVyR5dBzt2c3+Mb+gGXScU4Eg2lkMAsQg0jx2P7w5xHmT5BR6U29ZBnzU ytn/l07CJpWxFKhq0UDBysYiJordWq1m3zh3Bdjtccag0ngd8HLFElIPoCTGcurxV81D xF8zFvHg+XqQpcS+r65pYo78YmEUh2I0xzOUERBVn7qlSnRHnmjQlNqXFrNoE2tdFekC B1EyAiJ36JJZwiVm6bCWWTnUrEJgWY2Hugb4lZoO8Mf2+/ZEJ1aVaNtELntLhHG4QmVf ch+A== X-Gm-Message-State: APjAAAV0yaxSMYaW8+h22P7ceufu+A1bK7H1xMk6590lp+4rl2JaVX86 KCEFOVgSYAZlskxjF1Hp3EZjxQ== X-Google-Smtp-Source: APXvYqykfitYAG52vjSP8dzXF2FS8sDgJwmytLl4OTb2ohIaRLJL7rvH7SKJipbiRa1ad8ZaBLFvHQ== X-Received: by 2002:a17:902:820c:: with SMTP id x12mr5687503pln.216.1562862646816; Thu, 11 Jul 2019 09:30:46 -0700 (PDT) Received: from [172.21.92.139] ([38.119.166.65]) by smtp.gmail.com with ESMTPSA id j20sm5914373pfr.113.2019.07.11.09.30.45 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 11 Jul 2019 09:30:45 -0700 (PDT) Content-Type: multipart/alternative; boundary=Apple-Mail-109104EB-4406-4AC6-A485-9B736EA97B84 Mime-Version: 1.0 (1.0) From: Clem cole X-Mailer: iPhone Mail (16F203) In-Reply-To: Date: Thu, 11 Jul 2019 09:30:44 -0700 Content-Transfer-Encoding: 7bit Message-Id: <610F6FCB-F24D-4788-953A-83E0E6456622@ccc.com> References: <8235a090-c48a-4587-8974-23305233bc33@PU1APC01FT026.eop-APC01.prod.protection.outlook.com> <3CFC8159-08DD-4647-8CEF-FE8D196AB3C9@ccc.com> To: Jason Stevens Subject: Re: [TUHS] PCC for the i386 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@tuhs.org Errors-To: tuhs-bounces@minnie.tuhs.org Sender: "TUHS" --Apple-Mail-109104EB-4406-4AC6-A485-9B736EA97B84 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable 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 g= cc. =20 CSRG wanted the different backends for C. ThAts it. Besides the vax, Rms h= ad done 68000 and 386 back ends then. =20 With the original system V, all of AT&T, Intel and IBM paid Interactive Syst= ems Corp (aka ISC) to port the System V/Vax code to a 386 ps/2 and an Intel r= eference system that used an ISA bus. This would be eventually released in s= ource at the 386 port from AT&T. As part of the contract summit supplied t= he compiler I know the AT&T assembler with it=E2=80=99s backwards syntax from Intel was d= one before rms did his. He was compatible with the summit assembler. I don= =E2=80=99t remember who=E2=80=99s 386 backend came out first. I think is wa= s the summit compiler but you needed a system v license which UCB did not ha= ve.=20 Clem Sent from my PDP-7 Running UNIX V0 expect things to be almost but not quite.= =20 > On Jul 11, 2019, at 8:50 AM, Jason Stevens wrote: >=20 > That would make sense. I was able to find some info on PCC2 here >=20 > http://doc.cat-v.org/unix/unix-before-berkeley/ >=20 > I'm guessing along with the adoption of emacs the csrg must have been furt= her gnu synergy... Or maybe PCC2 just wasn't available outside of the labs?= =20 >=20 > Or maybe by '88 gcc was already usurping many of the c compilers of the er= a.=20 >=20 >=20 >=20 >=20 >=20 > On Thu, Jul 11, 2019 at 11:37 PM +0800, "Clem cole" wrote:= >=20 >> I believe the pcc/386 came out of Steve Johnson team at Summit with the P= CC2 work. =20 >>=20 >> Sent from my PDP-7 Running UNIX V0 expect things to be almost but not qui= te.=20 >>=20 >>> On Jul 11, 2019, at 7:53 AM, Jason Stevens wrote: >>>=20 >>> Does anyone know where the 386 port from PCC came from? >>> =20 >>> While trying to build a Tahoe userland for the i386, it seems that every= thing was built with GCC=E2=80=A6 >>> Was there a PCC for the i386 around =E2=80=9988-90? It seems after the r= apid demise of the Tahoe/Harris >>> HCX-9 that the non Vax/HCX-9 platforms had moved to GCC? >>> =20 >>> Also anyone know any good test software for LIBC? I=E2=80=99ve been tra= cing through some >>> strange issues rebuilding LIBC from Tahoe, where I had to include some b= its from >>> Reno to get diropen to actually work. I would imagine there ought to ha= ve 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 s= ure >>> its stable enough. --Apple-Mail-109104EB-4406-4AC6-A485-9B736EA97B84 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable By the time of 4.2 the switch from the &nbs= p;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.  Beside= s the vax, Rms had done 68000 and 386 back ends then.  

<= /div>
With the original system V, all of AT&T, Intel and IBM paid In= teractive 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 eve= ntually released in source at the 386 port from AT&T.   As part of t= he contract summit supplied the compiler

I know the= AT&T assembler with it=E2=80=99s backwards syntax from Intel was done b= efore rms did his.  He was compatible with the summit assembler.  = I don=E2=80=99t remember who=E2=80=99s 386 backend came out first.  I t= hink is was the summit compiler but you needed a system v license which UCB d= id not have. 

Clem

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

On Jul 11, 20= 19, at 8:50 AM, Jason Stevens <jsteve@superglobalmegacorp.com> wrote:

That would make sense.   I was able to find some info on PCC= 2 here

I'm guessing along with the a= doption of emacs the csrg must have been further gnu synergy...  Or may= be PCC2 just wasn't available outside of the labs?

Or maybe by '88 gcc was alre= ady usurping many of the c compilers of the era.





On Thu, Jul 11, 2019 at 11:37 PM +0800, "Clem col= e" <= 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&g= t; wrote:

Does anyone kn= ow where the 386 port from PCC came from?

&nb= sp;

While trying to build a Tahoe userland f= or the i386, it seems that everything was built with GCC=E2=80=A6

Was there a PCC for the i386 around =E2=80=9988-90?  It= seems after the rapid demise of the Tahoe/Harris

= HCX-9 that the non Vax/HCX-9 platforms had moved t= o GCC?

 

strange issues rebuilding LIBC from Tahoe, where I had to includ= e 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 w= orking instead of say

building as much as you can, and playing rogue for a few hou= rs to make sure

its stable enough.

= --Apple-Mail-109104EB-4406-4AC6-A485-9B736EA97B84--