From: Al Kossow <aek@bitsavers.org>
To: tuhs@tuhs.org
Subject: [TUHS] Re: On the uniqueness of DMR's C compiler
Date: Thu, 9 May 2024 13:57:18 -0700 [thread overview]
Message-ID: <b20f7075-f992-a7b8-40dc-32e572ad4fba@bitsavers.org> (raw)
In-Reply-To: <C7223B04-B299-475E-9EB2-03FA59CF0994@planet.nl>
On 5/9/24 1:40 PM, Paul Ruizendaal via TUHS wrote:
> - Unfortunately, I have not been able to find a description of the POPS IL.
I went down that rabbit hole researching why Don Knuth had a high opinion of it.
If you dig around, the IL is described in the SDS Fortran documentation
http://bitsavers.org/pdf/sds/9xx/lang/900883A_9300_FORTRAN_IV_Tech_Aug65.pdf
and http://bitsavers.org/pdf/digitek/Data_Structures_in_Digiteks_FORTRAN_IV_Compiler_for_the_SDS_900_Series.pdf
and a compiler listing
https://archive.computerhistory.org/resources/text/Knuth_Don_X4100/PDF_index/k-1-pdf/k-1-C1051-Digitek-FORTRAN.pdf
next prev parent reply other threads:[~2024-05-09 20:57 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
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 [this message]
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=b20f7075-f992-a7b8-40dc-32e572ad4fba@bitsavers.org \
--to=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).