From: Paul McJones <paul@mcjones.org>
To: Clem Cole <clemc@ccc.com>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: On the uniqueness of DMR's C compiler
Date: Wed, 8 May 2024 20:39:32 -0700 [thread overview]
Message-ID: <6CFD774F-F714-4AD0-A37E-E40013B8A281@mcjones.org> (raw)
In-Reply-To: <171519201646.4052234.694570138790187562@minnie.tuhs.org>
[-- Attachment #1: Type: text/plain, Size: 1570 bytes --]
> On Wed, 8 May 2024 14:12:15 -0400,Clem Cole <clemc@ccc.com <mailto:clemc@ccc.com>> wrote:
>
> 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.
Michael Powell at DEC WRL wrote a Modula 2 compiler that generated VAX code. Here’s an extract from announcement.d accompanying a 1992 release of the compiler from gatekeeper.dec.com <http://gatekeeper.dec.com/>:
The compiler was designed and built by Michael L. Powell, and originally
released in 1984. Joel McCormack sped the compiler up, fixed lots of bugs, and
swiped/wrote a User's Manual. Len Lattanzi ported the compiler to the MIPS.
Later, Paul Rovner and others at DEC SRC designed Modula-2+ (a language extension with exceptions, threads, garbage collection, and runtime type dispatch). The Modula-2+ compiler was originally based on Powell’s compiler. Modula-2+ ran on the VAX.
Here’s a DEC SRC research report on Modula-2+:
http://www.bitsavers.org/pdf/dec/tech_reports/SRC-RR-3.pdf
Modula-3 was designed at DEC SRC and Olivetti Labs. It had a portable implementation (using the GCC back end) and ran on a number of machines including Alpha.
Paul
[-- Attachment #2: Type: text/html, Size: 6837 bytes --]
next parent reply other threads:[~2024-05-09 3:39 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <171519201646.4052234.694570138790187562@minnie.tuhs.org>
2024-05-09 3:39 ` Paul McJones [this message]
2024-05-09 3:46 ` Warner Losh
[not found] <171535904627.4052234.5321502833323676423@minnie.tuhs.org>
2024-05-10 18:55 ` Paul McJones
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
-- strict thread matches above, loose matches on Subject: below --
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
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
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=6CFD774F-F714-4AD0-A37E-E40013B8A281@mcjones.org \
--to=paul@mcjones.org \
--cc=clemc@ccc.com \
--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).