The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] B Source Code
Date: Fri, 15 Sep 2017 09:03:20 -0400	[thread overview]
Message-ID: <CAC20D2PLcXT2dRY2FHP9J9ROb_8hRCcARt7fMK72kpX3DctadA@mail.gmail.com> (raw)
In-Reply-To: <CAC20D2PTwQ9jK_qt7ws60iRGd6qkUdY83BOLP7FixkxsUnqPAw@mail.gmail.com>

Also, in my Tektronix archives... we had an 11/60 with WSC and IIRC Steve
Glaser took a stab at moving the CMU stuff. The microengines between the
11/40 and 11/60 were different, so the code had to be rewritten. A big
issue, again IIRC, was the microcode compiler/tools for the WSC ran on RSX
so it meant UNIX was not running, which was not popular.

But around the same time, unexpected our group had the chance to get an
fairly loaded cast off seperate I/D based 11/70 which had been running
RSTS/Cobol for a business support team in sales.    By the time, Steve got
anything working on the 11/60, I had the 11/70 (aka "teklabs") up and
installed; and I don't remember what happened to the WSC stuff; since we
had better solution to small address space problem of adding a '17th
address bit' with hardware.

Clem

Clem

On Fri, Sep 15, 2017 at 8:44 AM, Clem Cole <clemc at ccc.com> wrote:

> CMU/CS implemented CSAV and CRET on the 11/40e (6th edition++).  IMO - it
> was a mixed bag.  I've forgotten the statistics, it was a few ticks fasters
> for saving the registers, which was good.   The primary thing it did was
> save a small amount of address space on the non-I/D 40  - which was helpful
> for applications as they got larger and were running out of address
> space...... But it was PITA in practice because it meant that binaries
> compiled on IUS and SUS (the UNIX two systems in CS), would not run
> anywhere else on campus which were mostly 11/34 or later 11/34A's and it a
> networked environment (which we were just starting to create) the seams
> tended to show a little more than we would have liked.
>
> IIRC I eventually got a emulator working at Mellon Institute and EE
> systems so they binaries would not core dump, but we just recompiled we ran
> into them.
>
> The real solution to address space issue was when DEC released the 11/44
> which was separate I/D (11/70 class) and the thunk work that we did in
> 2.9BSD in trying to move 4.1/4.2 code to the 11.
>
> FYI:  Danny Klein and I should have the compiler somewhere (and the
> microcode) is I ever get my CMU archives off tape.  It's on my list of
> things to look for.
>
> Clem
>
>
>
> On Thu, Sep 14, 2017 at 11:59 PM, Dave Horsfall <dave at horsfall.org> wrote:
>
>> 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 part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170915/0da58f8d/attachment.html>


  reply	other threads:[~2017-09-15 13:03 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
2017-09-19  1:20     ` Dave Horsfall
2017-09-15 12:44   ` Clem Cole
2017-09-15 13:03     ` Clem Cole [this message]
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=CAC20D2PLcXT2dRY2FHP9J9ROb_8hRCcARt7fMK72kpX3DctadA@mail.gmail.com \
    --to=clemc@ccc.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).