From: Paul Ruizendaal <pnr@planet.nl>
To: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Looking for final C compiler by Dennis Ritchie
Date: Mon, 23 Jul 2018 11:24:57 +0200 [thread overview]
Message-ID: <6E880974-2177-4DBA-A67C-20247478F5D0@planet.nl> (raw)
In-Reply-To: <CACXZuxeJ3igMtfbLs1iUPMLhomQUG0dEjpaHHmV0L7hF0bvo4g@mail.gmail.com>
> On 22 Jul 2018, at 22:49, Dibyendu Majumdar <mobile@majumdar.org.uk> wrote:
>
>>> I will try to port the C compiler to amd64 - while preserving as much of
>>> the original code as I can. But not sure if this is even feasible.
>>
>> If that is your goal, you might want to start with the version included with 2.11BSD. It is essentially the same as the version from V7, but with 15 more years of bug fixes. I used that source to port V6 Unix to the TI990 architecture back in 2014/2015 and the good thing about it is that it still compiles with a modern gcc.
>
> I found similarities between the 2.11BSD and 10th edition sources -
> presumably 2.11BSD was based on (or incorporated) changes in the 10th
> edition?
No, it derives from V7, with much stuff from 4BSD back-ported to the PDP11. See the “Early BSDs” section of the Unix Tree (https://minnie.tuhs.org//cgi-bin/utree.pl). Although V8 also has some 4BSD roots, the V8/V9/V10 lineage is different from the 2.8-2.11 BSD lineage. There was a lot of code sharing back then, it is not a simple picture.
> BTW did you publish your work?
https://1587660.websites.xs4all.nl/cgi-bin/9995/dir?ci=tip
next prev parent reply other threads:[~2018-07-23 9:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-20 10:04 Paul Ruizendaal
2018-07-20 19:57 ` Dibyendu Majumdar
2018-07-22 20:49 ` Dibyendu Majumdar
2018-07-23 9:24 ` Paul Ruizendaal [this message]
2018-07-23 10:28 ` arnold
2018-07-23 19:35 ` Dibyendu Majumdar
2018-07-24 6:37 ` arnold
2018-07-23 15:12 ` Clem Cole
2018-07-23 15:55 ` Larry McVoy
2018-07-23 19:29 ` Dibyendu Majumdar
2018-07-23 20:12 ` Bakul Shah
2018-07-23 20:48 ` Dibyendu Majumdar
-- strict thread matches above, loose matches on Subject: below --
2018-07-18 21:37 Dibyendu Majumdar
2018-07-19 5:41 ` arnold
2018-07-19 19:23 ` Dibyendu Majumdar
2018-07-20 22:04 ` Dibyendu Majumdar
2018-07-19 14:50 ` Clem Cole
2018-07-19 19:40 ` Dibyendu Majumdar
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=6E880974-2177-4DBA-A67C-20247478F5D0@planet.nl \
--to=pnr@planet.nl \
--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).