From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
To: tuhs@tuhs.org
Cc: jnc@mercury.lcs.mit.edu
Subject: [TUHS] Typesetter C compiler
Date: Thu, 2 Feb 2023 14:02:32 -0500 (EST) [thread overview]
Message-ID: <20230202190232.C79D118C073@mercury.lcs.mit.edu> (raw)
There was recent discussion here about the Typesetter C compiler; I don't
have the energy to look through the tons of opinion posts about recent
programming styles, to find the posts about actual Unix history which related
to that compiler, but I seem to recall that there was interest in locating
the source for it? I had strted to look, but then got distracted by some
other high-pri stuff; here are a few notes that I had accumulated to reply -
I hope they aren't too out-of-date by now.
I have a copy of it, from the dump of the CSR machine (I can't make the whole
dump public, sorry; it has personal material from a bunch of people mixed in).
I was pretty sure the C compiler from Mini-Unix, here:
https://minnie.tuhs.org/cgi-bin/utree.pl?file=Mini-Unix/usr/source/c
was from the right timeframe to be the Typesetter C, but a quick check of
c0.h, shows that it's not; that one seems to be more like the V6 one. (Ditto
for LSX.)
The PWB1 one:
https://minnie.tuhs.org/cgi-bin/utree.pl?file=PWB1/sys/c/c
seems, from a very quick look at c0.h (using that nice side-by-side compare
feature on the TUHS archive - thanks, Warren!), to be somewhat close to the
Typesetter C. It would be interesting to compare that one to the CSR one
(which definitely is) to be sure.
Also, the V7 C compiler (not pcc, but the PDP-11 one) seems to be a fairly
close relative, too.
Noel
next reply other threads:[~2023-02-02 19:02 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 19:02 Noel Chiappa [this message]
2023-02-02 21:57 ` [TUHS] " Jonathan Gray
2023-02-03 0:43 ` Jonathan Gray
2023-02-02 22:36 ` [TUHS] Proper use of TUHS (was Re: Typesetter C compiler) Dan Cross
2023-02-02 22:41 ` [TUHS] " Larry McVoy
2023-02-02 22:47 ` Jim Capp
2023-02-03 1:44 ` Dave Horsfall
2023-02-03 13:17 ` Alan D. Salewski
2023-02-03 13:55 ` Larry McVoy
2023-02-06 20:02 ` Chris Hanson
2023-02-03 14:11 ` Chet Ramey
2023-02-03 14:15 ` Larry McVoy
2023-02-03 16:39 ` Dan Cross
2023-02-03 16:54 ` Larry McVoy
2023-02-03 17:08 ` Dan Cross
2023-02-03 17:11 ` Steve Nickolas
2023-02-03 17:26 ` [TUHS] move to COFF " Will Senn
2023-02-03 17:31 ` [TUHS] " Will Senn
2023-02-03 17:45 ` [TUHS] " Bakul Shah
2023-02-05 10:42 ` steve jenkin
2023-02-04 8:03 ` [TUHS] A List for New Systems Influenced by History. (Was: Proper use of TUHS) Ralph Corderoy
2023-02-04 13:56 ` [TUHS] " Larry McVoy
2023-02-04 17:31 ` [TUHS] Re: A List for New Systems Influenced by History Angel M Alganza
2023-02-03 6:36 ` [TUHS] Re: Proper use of TUHS (was Re: Typesetter C compiler) Lars Brinkhoff
2023-02-04 22:38 ` Tomasz Rola
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=20230202190232.C79D118C073@mercury.lcs.mit.edu \
--to=jnc@mercury.lcs.mit.edu \
--cc=tuhs@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).