The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Clem Cole <clemc@ccc.com>
To: Al Kossow <aek@bitsavers.org>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: On the uniqueness of DMR's C compiler
Date: Wed, 8 May 2024 14:12:55 -0400	[thread overview]
Message-ID: <CAC20D2PedGJ3RKcyRN6awj0wLr-UBSupbsbtqdHVAFC_yAHy-w@mail.gmail.com> (raw)
In-Reply-To: <CAC20D2PwdHJhysU022X=Rk3VicqbgmUWH1dF+QxT6BnWvbQUxg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2067 bytes --]

s/Beety/Beatty/  -- sorry
ᐧ

On Wed, May 8, 2024 at 2:12 PM Clem Cole <clemc@ccc.com> wrote:

>
>
> On Wed, May 8, 2024 at 1:46 PM Al Kossow <aek@bitsavers.org> wrote:
>
>> Thoth has been a white whale for me for decades.
>
> Ditto.  Although, I believe the late John Beety had his 'Thoth Thucks" tee
> shirt for years.  I believe Kelly Booth still does.
>
>
>
>> AFAIK nothing has survived from it.
>>
> You can argue that V-Kernel and QNX are children of Thoth - but they were
> both in a flavor of Waterloo C that did not think ever targeted the PDP-11
> [that might be a misunderstanding WRT Waterloo C].
>
>>
>> "Decus" (Conroy's) C (transliteration of the assembler Unix C) should
>> also be mentioned.
>>
> Hmmmm, it's a flavor of Dennis' compiler in disguise and was sort of an
> end-around for the AT&T lawyers by taking the *.s files, and converting
> them to MACRO11, and then
> redoing the assembler code to use originally RT11 I/O and later RSX11.
> That said, it had its own life and ran on the DEC OSses, not UNIX, so it
> probably counts.
> That said, I thought Paul was asking about different core compiler
> implementations, and I would argue the DECUS/Conroy compiler is the DMR
> compiler, while the list I offered was all different core implementations.
>
> I'm curious about Jon and Tom's MOD2 compiler.   Other than Wirth's, which
> targeted the 68000, Lilith, and VAX, I did not know of another for the
> PDP-11.  Any idea of its origin story? I would have expected it to have
> derived from Wirth's Modula subsystem.  FWIW:  The DEC Mod-II and Mod-III
> were new implementations from DEC WRL or SRC (I forget).  They targeted
> Alpha and I, maybe Vax.  I'd have to ask someone like Larry Stewart or Jeff
> Mogul who might know/remember, but I thought that the font end to the DEC
> MOD2 compiler might have been partly based on Wirths but rewritten and by
> the time of the MOD3 FE was a new one originally written using the previous
> MOD2 compiler -- but I don't remember that detail.
>

[-- Attachment #2: Type: text/html, Size: 4085 bytes --]

  reply	other threads:[~2024-05-08 18:13 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-07 20:59 [TUHS] " Paul Ruizendaal
2024-05-07 22:07 ` [TUHS] " Rob Pike
2024-05-08  9:35   ` Paul Ruizendaal
2024-05-08 13:12     ` Rob Pike
2024-05-08 15:51     ` Clem Cole
2024-05-08 16:07       ` Jon Forrest
2024-05-08 17:49         ` Tom Perrine
2024-05-08 17:05       ` Adam Sampson
2024-05-08 17:45       ` Al Kossow
2024-05-08 18:12         ` Clem Cole
2024-05-08 18:12           ` Clem Cole [this message]
2024-05-09  1:27           ` Lawrence Stewart
2024-05-31 12:00       ` Paul Ruizendaal
2024-05-31 12:21         ` Peter Yardley
2024-05-08 11:09 ` Michael Kjörling
2024-05-09 20:40 ` Paul Ruizendaal via TUHS
2024-05-09 20:57   ` Al Kossow
2024-05-08 18:29 Douglas McIlroy
2024-05-10 17:28 ` Paul Winalski
2024-05-11  9:16   ` Ralph Corderoy
2024-05-11 13:42   ` G. Branden Robinson
     [not found] <171519201646.4052234.694570138790187562@minnie.tuhs.org>
2024-05-09  3:39 ` Paul McJones
2024-05-09  3:46   ` Warner Losh
     [not found] <171535904627.4052234.5321502833323676423@minnie.tuhs.org>
2024-05-10 18:55 ` Paul McJones

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=CAC20D2PedGJ3RKcyRN6awj0wLr-UBSupbsbtqdHVAFC_yAHy-w@mail.gmail.com \
    --to=clemc@ccc.com \
    --cc=aek@bitsavers.org \
    --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).