The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: dave@horsfall.org (Dave Horsfall)
Subject: [TUHS] Harvard and Von Neumann Architectures and Unix
Date: Sun, 26 Nov 2017 10:15:23 +1100 (EST)	[thread overview]
Message-ID: <alpine.BSF.2.21.1711260955170.780@aneurin.horsfall.org> (raw)
In-Reply-To: <A2DB3F5E-70CC-413C-8B7C-3CCE451B1F37@cheswick.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1026 bytes --]

On Sat, 25 Nov 2017, William Cheswick wrote:

> On CDC machines, the return jump (RJ) instruction generally used to call 
> subroutines deposited a jump instruction (EQ B0,B0,caller+1) in the 
> called routine and jumped to the word after it.  Clearly, languages like 
> Pascal didn’t use that.

Ahhh; that brings back fond memories of my Cyber-72 days, and how easily 
we CompSci kiddies broke into KRONOS...[*]

One of my favourite machines was the PDP-8; the JSR instruction planted 
the return address in the first word and jumped to the second word, with a 
return being done (IIRC) by an indirect jump to the first word. 
Recursion?  What's that?

[*]
Can't remember it now, but (on an LA-36 Duckwriter) it was something like:

     COMMON POOL
     RELEASE POOL
     (intr)

     (Could be abbreviated to "COMMO POO" and "REL POO" for those with a
     sick sense of humour, which was most of us.)

and you got system privileges...

-- 
Dave Horsfall DTM (VK2KFU)  "Those who don't understand security will suffer."


  reply	other threads:[~2017-11-25 23:15 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-24 21:43 Noel Chiappa
2017-11-24 21:50 ` Jon Steinhart
2017-11-25 21:55   ` William Cheswick
2017-11-25 23:15     ` Dave Horsfall [this message]
2017-11-24 22:20 ` Mike Markowski
2017-11-24 22:31   ` Dave Horsfall
  -- strict thread matches above, loose matches on Subject: below --
2017-11-27 17:11 Noel Chiappa
2017-11-28  0:23 ` Dave Horsfall
2017-11-27 16:11 Noel Chiappa
2017-11-27 16:50 ` Larry McVoy
2017-11-27 17:08   ` Clem Cole
2017-11-27 18:21     ` Lawrence Stewart
2017-11-27 18:30       ` Lars Brinkhoff
2017-11-27 18:14   ` Warner Losh
2017-11-27 18:26     ` Paul Winalski
2017-11-27 17:35 ` Ian Zimmerman
2017-11-28 14:55 ` Tim Bradshaw
2017-11-28 19:45   ` Paul Winalski
2017-11-25 17:34 Doug McIlroy
2017-11-25 14:24 Noel Chiappa
2017-11-25 15:58 ` Lawrence Stewart
2017-11-25 16:10 ` Lars Brinkhoff
2017-11-25 19:59 ` Steve Simon
2017-11-25 21:59 ` Bakul Shah
2017-11-25  3:14 Doug McIlroy
2017-11-25  4:16 ` Jon Steinhart
2017-11-25  5:17   ` ron minnich
2017-11-25 14:23 ` Ralph Corderoy
2017-11-24 19:25 Will Senn
2017-11-24 19:28 ` Jon Steinhart
2017-11-27 14:50 ` Tony Finch

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=alpine.BSF.2.21.1711260955170.780@aneurin.horsfall.org \
    --to=dave@horsfall.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).