The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Rich Morin <rdm@cfcl.com>
To: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] A New History of Modern Computing - my thoughts
Date: Wed, 1 Dec 2021 00:46:41 -0800	[thread overview]
Message-ID: <D7F6EAFD-8053-4CD8-91AC-43F32049FE20@cfcl.com> (raw)
In-Reply-To: <20211130192718.C0401210F4@orac.inputplus.co.uk>

> On Nov 30, 2021, at 11:27, Ralph Corderoy <ralph@inputplus.co.uk> wrote:
> 
> ... The point of that bit of history is they were not chip designers, but
> knew electronics and programming.  Wilson designed the ARM's instruction
> set and it was a delight to code: very orthogonal, and every instruction
> had four-bits of condition-flag test, e.g. Carry Set, and a bit to
> indicate if this instruction should set the condition flags.  Thus
> several instructions in a row could test the condition flags set by an
> instruction a few earlier and unaltered since; this cut the need for
> quite a few branches. ...

I wrote a fair amount of PDP-11 assembler, back in the early 70's (about 10K LOC).  I was particularly happy with a routine that moved a cell between a pair of doubly-linked, circular linked lists (a "free" list and a "busy" list).

The routine only had to modify six pointers, which isn't a hard problem.  The cute part was that it was able to do so using (IIRC) only eight or nine instructions.  The PDP-11's auto-increment mode obviated the need for separate index modification code.

I had previously written a fair amount of code for a Varian 620i, which had an AQX architecture.  The 620i wasn't _hard_ to program, but it _was_ a bit tedious. The PDP-11, by comparison, was a programmer's delight.

Which brings me to a historical notion:

The DG Nova (https://en.wikipedia.org/wiki/Data_General_Nova) came out in 1969, just a bit before the PDP-11 (https://en.wikipedia.org/wiki/PDP-11).  My impression, when I (later on) looked at the Nova ISA, was that they had moved in the right direction from the AQX approach, but not quite far enough.  DEC, IMNSHO, got it right.  (ducking).

-r




  reply	other threads:[~2021-12-01  8:49 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-28 20:26 Jon Steinhart
2021-11-28 21:07 ` Rob Pike
2021-11-28 21:15   ` Jon Steinhart
2021-11-28 21:31     ` Ken Thompson
2021-11-28 21:47       ` Jon Steinhart
2021-11-28 22:17         ` Rob Pike
2021-11-29  0:19           ` Clem Cole
2021-11-29  1:12             ` Larry McVoy
2021-11-29  2:23               ` Bakul Shah
2021-11-30 19:27                 ` Ralph Corderoy
2021-12-01  8:46                   ` Rich Morin [this message]
2021-12-01 12:28                     ` Al Kossow
2021-11-30  3:18               ` Larry McVoy
2021-11-29  1:18             ` George Michaelson
2021-11-29  1:36             ` Bakul Shah
2021-11-29  1:47       ` Bakul Shah
2021-11-29  7:46         ` arnold
2021-11-29  7:52           ` arnold
2021-11-29 14:44             ` Larry McVoy
2021-11-29 12:11         ` Michael Kjörling
2021-11-28 21:23   ` Thomas Paulsen
2021-11-28 21:39     ` Steve Nickolas
2021-11-28 22:41       ` Ron Natalie
2021-11-28 21:40   ` Larry McVoy
2021-11-29 15:37 ` Phil Budne
2021-11-28 23:12 Noel Chiappa
2021-11-28 23:35 ` Adam Thornton
2021-11-29  1:53   ` John Cowan
2021-11-29 13:48   ` Dan Halbert

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=D7F6EAFD-8053-4CD8-91AC-43F32049FE20@cfcl.com \
    --to=rdm@cfcl.com \
    --cc=tuhs@minnie.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).