From: pechter@gmail.com (William Pechter)
Subject: [TUHS] B Source Code
Date: Fri, 15 Sep 2017 07:43:19 -0400 [thread overview]
Message-ID: <fbf3c0c5-e24a-46d0-a245-56559532c963.maildroid@localhost> (raw)
In-Reply-To: <alpine.BSF.2.21.1709151351010.89458@aneurin.horsfall.org>
I thought Reuters re-microcoded them to be the fastest PDP8 around...
So was the DEC Field Service story...
Bill
-----Original Message-----
From: Dave Horsfall <dave@horsfall.org>
To: The Eunuchs Hysterical Society <tuhs at tuhs.org>
Sent: Fri, 15 Sep 2017 0:00
Subject: Re: [TUHS] B Source Code
On Thu, 14 Sep 2017, Noel Chiappa wrote:
> Interesting factoid: The PDP-11 initially used a threaded FORTRAN
> implementation. In line with the observation above (about a new virtual
> machine), DEC actually looked into writing microcode for the -11/60
> (which had a writeable control store) to implement the FORTRAN virtual
> machine.
Did anyone actually use the WCS? I had visions of implementing CSAV and
CRET on our -60, but never did get around to it. Too late now...
--
Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer."
next prev parent reply other threads:[~2017-09-15 11:43 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-14 13:39 Noel Chiappa
2017-09-14 14:24 ` Dan Cross
2017-09-14 19:46 ` Derek Fawcus
2017-09-15 3:59 ` Dave Horsfall
2017-09-15 11:43 ` William Pechter [this message]
2017-09-19 1:20 ` Dave Horsfall
2017-09-15 12:44 ` Clem Cole
2017-09-15 13:03 ` Clem Cole
2017-09-15 14:16 ` [TUHS] Rich's B compiler, was " Tony Finch
-- strict thread matches above, loose matches on Subject: below --
2017-09-15 15:21 [TUHS] " Noel Chiappa
2017-09-14 3:48 Doug McIlroy
2017-09-14 4:49 ` Larry McVoy
2017-09-14 5:06 ` Lars Brinkhoff
2017-09-14 12:53 ` Ronald Natalie
2017-09-14 5:33 ` Alec Muffett
2017-09-14 5:44 ` Warner Losh
2017-09-12 18:03 Robert Swierczek
2017-09-12 18:14 ` Clem Cole
2017-09-12 19:24 ` Clem Cole
2017-09-12 19:43 ` Steve Johnson
2017-09-18 21:45 ` Angelo Papenhoff
2017-09-19 17:01 ` Thorsten Sideboard
2017-09-12 19:36 ` Charles Anthony
2017-09-12 20:39 ` Robert Swierczek
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=fbf3c0c5-e24a-46d0-a245-56559532c963.maildroid@localhost \
--to=pechter@gmail.com \
/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).