From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: tuhs-bounces@minnie.tuhs.org X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,HTML_FONT_LOW_CONTRAST, HTML_MESSAGE,MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.1 Received: from minnie.tuhs.org (minnie.tuhs.org [45.79.103.53]) by inbox.vuxu.org (OpenSMTPD) with ESMTP id 8ba32e5d for ; Thu, 19 Jul 2018 14:51:45 +0000 (UTC) Received: by minnie.tuhs.org (Postfix, from userid 112) id 13EAB9ED43; Fri, 20 Jul 2018 00:51:44 +1000 (AEST) Received: from minnie.tuhs.org (localhost [127.0.0.1]) by minnie.tuhs.org (Postfix) with ESMTP id B55B49E982; Fri, 20 Jul 2018 00:51:11 +1000 (AEST) Authentication-Results: minnie.tuhs.org; dkim=pass (1024-bit key; unprotected) header.d=ccc.com header.i=@ccc.com header.b=cKexTnAf; dkim-atps=neutral Received: by minnie.tuhs.org (Postfix, from userid 112) id EADAD9E3BA; Fri, 20 Jul 2018 00:51:07 +1000 (AEST) Received: from mail-io0-f175.google.com (mail-io0-f175.google.com [209.85.223.175]) by minnie.tuhs.org (Postfix) with ESMTPS id 57D3E9E3A6 for ; Fri, 20 Jul 2018 00:51:07 +1000 (AEST) Received: by mail-io0-f175.google.com with SMTP id y10-v6so7295472ioa.10 for ; Thu, 19 Jul 2018 07:51:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ccc.com; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=QBDdnqD6d0FfVxiSOiTEUHlUwIoX3tg9qkGrq0IkwKA=; b=cKexTnAfe1lVQdoGZIhtYLonUH+gS7K5mP3eoIHT+8W4SceOnBtRrwZ2cwTZqPJCn+ Q2gntJXgWG1qAWAAkeF0zoRM7PymYwy6qb9I8Ety5qkjI/z0+qne2czYmfa8yfabqLCu opxlDi+stdTLT9RihjeqW0xj61vssuWL3uj+0= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=QBDdnqD6d0FfVxiSOiTEUHlUwIoX3tg9qkGrq0IkwKA=; b=b3XSerm7IWf5uOO9rXITr/DsAn5XPoEJGCQwNVAWTui/3ojH71twPuTxeV0g8BjgsT XU+ix8+5DBywzhl7xSOctfyQK7lFM87QEVI971CjngqQh5yQKXNkBQ2x7fGRwI4JNJJ+ Zu4FXGisFY6w8XxOeRwNyp8btvw/BuK21mzPBnuEJFLpA+hfEjbZ+ItHKEIsmKKrRkzJ pJteZaRb3pNfs7+IVZHEbIZWpAAindrsmYu2VlgCvkCJlr8g5NCq7bglBwrPNCSpB3OT QGWoofZNyYgl3i/BFnDaIPGM7Ay21/jHN6+zcNJCRTkCNnKIu9KBRcj6j+YUZ6Wejbml J3pg== X-Gm-Message-State: AOUpUlGj4eKHA+Y8UPiCRY+r2n5SABkG+7GvX6LZAxMNHlx8dRu8oJji ovaGrjn8dvva3lauj/zfNjhirXLvA55M5cZenZPTFkdKf4E= X-Google-Smtp-Source: AA+uWPxy8zJs7nR3wlTsNUWy9uDITzWiwXiCWjx0SY40Pmyjmy/3f1D6gBQhwVuZ2ZD5VdiWGNK6D7MOoVG2e8hYtTo= X-Received: by 2002:a6b:9651:: with SMTP id y78-v6mr9032674iod.283.1532011866491; Thu, 19 Jul 2018 07:51:06 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a4f:8e56:0:0:0:0:0 with HTTP; Thu, 19 Jul 2018 07:50:35 -0700 (PDT) In-Reply-To: References: From: Clem Cole Date: Thu, 19 Jul 2018 10:50:35 -0400 Message-ID: To: Dibyendu Majumdar Content-Type: multipart/alternative; boundary="000000000000182a4505715b4fa1" Subject: Re: [TUHS] Looking for final C compiler by Dennis Ritchie X-BeenThere: tuhs@minnie.tuhs.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: The Unix Heritage Society mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: TUHS main list Errors-To: tuhs-bounces@minnie.tuhs.org Sender: "TUHS" --000000000000182a4505715b4fa1 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, Jul 18, 2018 at 5:37 PM, Dibyendu Majumdar wrote: > Hi > > I am interested in finding out if the last C compiler code (not the > earliest versions which I know > are available) written by Dennis Ritchie is available somewhere. I > assume that the C compiler in V7 code was written by him? > > Thanks and Regards > Dibyendu > =E2=80=8BI'm not sure if this is the last. This is a pointer to the V7 Ri= tchie Compiler: https://minnie.tuhs.org//cgi-bin/utree.pl?file=3DV7/usr/src/cmd/= c - The sources and the makefile build the three passes /lib/c[012] This should be a good starting point/base line. Be careful because the Johnson Compiler (pcc) was also included with V7 and is a different technology. This is important because their are modifications to both the Ritchie and Johnson compilers 'in-the-wild' for other back-ends and new optimizations. I for instance, re-targeted the Ritchie compiler to what would become the 68000 (it was not yet numbered, it was an experimental chip when we had access to it in the late 1970s in Tek Labs - mine was a 16 bit 'int' as I was coming primarily from the PDP-11 at the time and the chip was a 16 bit chip internally - so the code was tight and clean and I basically substituted PDP-11 instruction sequences for 68000 sequences). IIRC, Jack Test's 68000 compiler from MIT which was about 18 mons later was based on the Johnson compiler but he used a 32 bit 'int' which proved easier for porting programs from the Vax, as the chip supported 32 bit words even though it took 2 ticks to do anything [so Jack's compiler generated slower code for many simple ops]. I recommend, that google for the old USENIX tapes and see what you turn up and compare. =E1=90=A7 --000000000000182a4505715b4fa1 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Wed, Jul 18, 2018 at 5:37 PM, Dibyendu Majumdar <mo= bile@majumdar.org.uk> wrote:
Hi

I am interested in finding out if the last C compiler code (not the
earliest versions which I know
are available) written by Dennis Ritchie is available somewhere. I
assume that the C compiler in V7 code was written by him?

Thanks and Regards
Dibyendu
=E2=80=8BI'm not sure if this i= s the last.=C2=A0 =C2=A0This is a pointer to the V7 Ritchie Compiler:=C2=A0= https://minnie.tuhs.org//cgi-bin/utree.pl?file=3DV7/usr/src/cmd/c= =C2=A0 - The sources and the makefile build the three passes /lib/c[012]=C2= =A0=C2=A0
This should be a good starting = point/base line.

Be careful because the Johnson Compiler (pcc) was also inclu= ded with V7 and is a different technology.=C2=A0=C2=A0

This is important beca= use their are modifications to both the Ritchie and Johnson compilers '= in-the-wild' for other back-ends and new optimizations.=C2=A0 =C2=A0 I = for instance, re-targeted the Ritchie compiler to what would become the 680= 00 (it was not yet numbered, it was an experimental chip when we had access= to it in the late 1970s in Tek Labs - mine was a 16 bit 'int' as I= was coming primarily from the PDP-11 at the time and the chip was a 16 bit= chip internally - so the code was tight and clean and I basically substitu= ted PDP-11 instruction sequences for 68000 sequences).=C2=A0 =C2=A0IIRC, Ja= ck Test's 68000 compiler from MIT which was about 18 mons later was bas= ed on the Johnson compiler but he used a 32 bit 'int' which proved = easier for porting programs from the Vax, as the chip supported 32 bit word= s even though it took 2 ticks to do anything [so Jack's compiler genera= ted slower code for many simple ops].
I recommend, that google for the old US= ENIX tapes and see what you turn up and compare.

3D"==E1=90=A7
--000000000000182a4505715b4fa1--