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.0 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, HEADER_FROM_DIFFERENT_DOMAINS,HTML_MESSAGE,MAILING_LIST_MULTI, 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 0e1ea24b for ; Thu, 11 Jul 2019 15:51:12 +0000 (UTC) Received: by minnie.tuhs.org (Postfix, from userid 112) id 3940E948EB; Fri, 12 Jul 2019 01:51:11 +1000 (AEST) Received: from minnie.tuhs.org (localhost [127.0.0.1]) by minnie.tuhs.org (Postfix) with ESMTP id D9EAD9480A; Fri, 12 Jul 2019 01:50:44 +1000 (AEST) Authentication-Results: minnie.tuhs.org; dkim=pass (1024-bit key; unprotected) header.d=outdoorexpressionslimited.onmicrosoft.com header.i=@outdoorexpressionslimited.onmicrosoft.com header.b="eGfkUNCE"; dkim-atps=neutral Received: by minnie.tuhs.org (Postfix, from userid 112) id E537A9480A; Fri, 12 Jul 2019 01:50:41 +1000 (AEST) Received: from APC01-HK2-obe.outbound.protection.outlook.com (mail-eopbgr1300043.outbound.protection.outlook.com [40.107.130.43]) by minnie.tuhs.org (Postfix) with ESMTPS id 4C50C947D8 for ; Fri, 12 Jul 2019 01:50:40 +1000 (AEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outdoorexpressionslimited.onmicrosoft.com; s=selector1-outdoorexpressionslimited-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=6L0V8sMV6bbeaaivWgLjcS0VuVFYj2/rICG9YIIrVNo=; b=eGfkUNCEv0L6MU1q/3NMp3p2shoRmNQ5IhkGOsaRefJPHrEC0JFe8pFT6/H4UqTIhBeQP9TzVIVdO2MNs41D2HDIh48xANhOA4XqmvVaayKXQXPq62k0EwX3Owy0Os2CIbtUeeQgHL0vTF5r7HXCxOcFKwOjAM6YpERGAGrrAaQ= Received: from PS2PR02CA0028.apcprd02.prod.outlook.com (2603:1096:300:59::16) by SG2PR0201MB2079.apcprd02.prod.outlook.com (2603:1096:3:7::23) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2052.19; Thu, 11 Jul 2019 15:50:35 +0000 Received: from PU1APC01FT003.eop-APC01.prod.protection.outlook.com (2a01:111:f400:7ebd::206) by PS2PR02CA0028.outlook.office365.com (2603:1096:300:59::16) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2073.10 via Frontend Transport; Thu, 11 Jul 2019 15:50:34 +0000 Authentication-Results: spf=fail (sender IP is 59.148.14.54) smtp.mailfrom=superglobalmegacorp.com; ccc.com; dkim=none (message not signed) header.d=none;ccc.com; dmarc=none action=none header.from=superglobalmegacorp.com; Received-SPF: Fail (protection.outlook.com: domain of superglobalmegacorp.com does not designate 59.148.14.54 as permitted sender) receiver=protection.outlook.com; client-ip=59.148.14.54; helo=exchange.superglobalmegacorp.local; Received: from exchange.superglobalmegacorp.local (59.148.14.54) by PU1APC01FT003.mail.protection.outlook.com (10.152.252.95) with Microsoft SMTP Server id 15.20.2052.18 via Frontend Transport; Thu, 11 Jul 2019 15:50:32 +0000 Received: from mail.outlook.com (joes-20dollar-tunnel [10.5.11.1]) by exchange.superglobalmegacorp.local with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72) id NPGTFFMB; Thu, 11 Jul 2019 23:50:31 +0800 Date: Thu, 11 Jul 2019 15:50:29 +0000 From: Jason Stevens To: Clem cole Message-ID: In-Reply-To: <3CFC8159-08DD-4647-8CEF-FE8D196AB3C9@ccc.com> References: <8235a090-c48a-4587-8974-23305233bc33@PU1APC01FT026.eop-APC01.prod.protection.outlook.com> <3CFC8159-08DD-4647-8CEF-FE8D196AB3C9@ccc.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_4878_1471342675.1562860229555" X-Mailer: Outlook for iOS and Android X-EOPAttributedMessage: 0 X-Forefront-Antispam-Report: CIP:59.148.14.54; IPV:NLI; CTRY:HK; EFV:NLI; SFV:NSPM; SFS:(10009020)(136003)(346002)(396003)(39830400003)(376002)(2980300002)(1110001)(339900001)(189003)(199004)(356004)(126002)(11346002)(446003)(4326008)(476003)(16586007)(486006)(81166006)(33964004)(966005)(8676002)(86362001)(53546011)(508600001)(81156014)(5660300002)(7696005)(76176011)(55016002)(54896002)(2906002)(6306002)(6916009)(85226003)(336012)(70206006)(70586007)(9686003)(236005)(229853002)(6246003)(186003)(316002)(36906005)(8936002)(53416004)(50226002)(606006)(105606002)(26005)(71190400001); DIR:OUT; SFP:1101; SCL:1; SRVR:SG2PR0201MB2079; H:exchange.superglobalmegacorp.local; FPR:; SPF:Fail; LANG:en; PTR:059148014054.ctinets.com; MX:1; A:1; X-MS-PublicTrafficType: Email X-MS-Office365-Filtering-Correlation-Id: 07df4da9-7fa6-4d78-af11-08d706178205 X-Microsoft-Antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(7021145)(8989299)(4534185)(7022145)(4603075)(4627221)(201702281549075)(8990200)(7048125)(7024125)(7027125)(7023125)(5600148)(711020)(4605104)(1401327)(2017052603328); SRVR:SG2PR0201MB2079; X-MS-TrafficTypeDiagnostic: SG2PR0201MB2079: X-MS-Exchange-PUrlCount: 1 X-Microsoft-Antispam-PRVS: X-MS-Oob-TLC-OOBClassifiers: OLM:8882; X-Forefront-PRVS: 0095BCF226 X-MS-Exchange-SenderADCheck: 1 X-Microsoft-Antispam-Message-Info: g/m6f0scyOYlsSQFqB6ar6NLv2CT0FjDg3RoQJM5LWeJLnN8nwtmYZHg9WVLTQqV/hcSgzHXG03QYPNYF8+LRPEuA2XLTkW8OGzicucknBjU3O7b4qQG8pr4V/raxyO7K1DT2PnhDzwYAEs1ogvLTyg2jxMWmj9cmN57kwVt58z+15yVVJeWYdOrGy8waTFoHJTw6b6kq0/t4MEyo7lgXqisJ+Z5SRJkSbaltwHMjHMW0oxvvw+xqBhk52YhMM87DKebYjg1NpWoGpME5iAtXfJxut6KDsFs0aTEQIcwPd7WeOEpu6dUjT1L3mjAEASSDhG3FtyeDtabvOLKV4URO8ZgJFNjF6TwV0nGL0Ez1M7RzcdAS56OLJ2iAzeRVjvXXfrs5mAIPQPvvgvPwystXwIC0aw7eYDoj2XB0oVWIKI= X-OriginatorOrg: superglobalmegacorp.com X-MS-Exchange-CrossTenant-OriginalArrivalTime: 11 Jul 2019 15:50:32.6785 (UTC) X-MS-Exchange-CrossTenant-Network-Message-Id: 07df4da9-7fa6-4d78-af11-08d706178205 X-MS-Exchange-CrossTenant-Id: 870ed452-0577-4b7b-90ed-9cac080031b9 X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=870ed452-0577-4b7b-90ed-9cac080031b9; Ip=[59.148.14.54]; Helo=[exchange.superglobalmegacorp.local] X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem X-MS-Exchange-Transport-CrossTenantHeadersStamped: SG2PR0201MB2079 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" ------=_Part_4878_1471342675.1562860229555 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable That would make sense.=C2=A0=C2=A0 I was able to find some info on PCC2 her= e http://doc.cat-v.org/unix/unix-before-berkeley/ I'm guessing along with the adoption of emacs the csrg must have been furth= er gnu synergy...=C2=A0 Or maybe PCC2 just wasn't available outside of the = labs?=20 Or maybe by '88 gcc was already usurping many of the c compilers of the era= .=20 On Thu, Jul 11, 2019 at 11:37 PM +0800, "Clem cole" wrote: I believe the pcc/386 came out of Steve Johnson team at Summit with the PCC= 2 work. =C2=A0 Sent from my PDP-7 Running UNIX V0 expect things to be almost but not quite= .=C2=A0 On Jul 11, 2019, at 7:53 AM, Jason Stevens = wrote: Does anyone know where the 386 port from PCC came from? =C2=A0 While trying to build a Tahoe userland for the i386, it seems that everythi= ng was built with GCC=E2=80=A6 Was there a PCC for the i386 around =E2=80=9988-90?=C2=A0 It seems after th= e rapid demise of the Tahoe/Harris HCX-9 that the non Vax/HCX-9 platforms had moved to GCC? =C2=A0 Also anyone know any good test software for LIBC?=C2=A0 I=E2=80=99ve been t= racing through some strange issues rebuilding LIBC from Tahoe, where I had to include some bits= from Reno to get diropen to actually work.=C2=A0 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.=20 ------=_Part_4878_1471342675.1562860229555 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
T= hat would make sense.   I was able to find some info on PCC2 here=

I'm guessing along with th= e 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 al= ready usurping many of the c compilers of the era.





On Thu, Jul 11, 2019 at 11:37 PM +0800, "Clem co= le" <clemc@ccc.com> wrote:

I believe the pcc/386 came out of Steve Johnson team at Summit with the PCC= 2 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.co= m> wrote:

Does anyone k= now where the 386 port from PCC came from?

&= nbsp;

While trying to build a Tahoe userlan= d for 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?&nbs= p; 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= =E2=80=99ve 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.&n= bsp; I would imagine there ought to have been some

platform exercise code to ma= ke 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.

=
------=_Part_4878_1471342675.1562860229555--