The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: dmr@plan9.bell-labs.com (dmr@plan9.bell-labs.com)
Subject: [TUHS] (no subject)
Date: Wed, 22 Feb 2006 00:08:57 -0500	[thread overview]
Message-ID: <713800fd0bb6afb1eb6ee39dcec5fe7c@plan9.bell-labs.com> (raw)

 > If I remember correctly, all of the "real" members of the 3B family
 > (i.e. 3B2, 3B5, 3B15 and 3B20) shared a common "virtual"
 > instruction set called (I think) IS25 - it was the job of the assembler
 > to translate IS25 into the actual machine code for the specific
 > processor used in each machine.

 > IS25 was a little curious because it only defined those instructions
 > that were likely to be of use to the C compiler - thus there was a
 > "push" instruction so that the compiler could push function arguments
 > onto the stack, but no "pop" instruction because the C compiler
 > never generated it.

IS25: just so. I managed to retrieve the scanned PDF for
the manual for this virtual instruction set.  It's an
internal memo, but I'll send it if anyone asks.  It's
2.8MB of page images and is 108 pages long.

The memories of Lindsly and Lowenstein are also apposite.
AT&T donated quite a few machines (3B20 and 3B2) to universities,
and though they appreciated the thought, there were
various drawbacks--the gift didn't include maintenance, for
example.

	Dennis



             reply	other threads:[~2006-02-22  5:08 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-22  5:08 dmr [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-01-11 23:02 Douglas McIlroy
2021-04-05 22:43 M Douglas McIlroy
2021-04-06  7:23 ` arnold
2021-04-06 23:25 ` Dave Horsfall
2021-04-07  1:01   ` Jon Steinhart
2015-12-26  4:51 Doug McIlroy
2015-12-26  4:49 Doug McIlroy
2015-12-24 18:09 scj
2015-12-24 18:09 scj
2015-07-19 20:55 Brian Walden
2015-07-18 17:43 Mark Longridge
2015-07-18 17:53 ` Larry McVoy
2015-07-19  0:57   ` Warren Toomey
2015-07-19  1:13     ` Larry McVoy
2015-07-19  1:19       ` Milo Velimirovic
2010-01-13  3:42 Larry McVoy
2005-07-20 21:17 Brantley Coile
2003-05-23  4:10 Dennis Ritchie
2003-05-24  3:42 ` Kenneth Stailey

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=713800fd0bb6afb1eb6ee39dcec5fe7c@plan9.bell-labs.com \
    --to=dmr@plan9.bell-labs.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).