The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
To: tuhs@tuhs.org
Cc: jnc@mercury.lcs.mit.edu
Subject: [TUHS] Re: who invented the link register
Date: Tue, 25 Oct 2022 18:52:51 -0400 (EDT)	[thread overview]
Message-ID: <20221025225251.6FC1818C073@mercury.lcs.mit.edu> (raw)

    > From: ron minnich

    > I know branch and link was in the 360; was it earlier?

Well, as I understand it, branch and link (BAL and BALR) did a couple of
different things (if I have this wrong, I hope someone will correct me). It
was a subroutine call, but it also loaded a base register.

(Those were used to deal with the /360's bizarro memory management, which was
not 'base and bounds, with a user's virtual address space starting at zero',
like a lot of contemporary machines. Rather, a process saw its actual physical
memory location, so depending on where in memoty a process was loaded, it
would be executing at different addresses visible to it; the base registers
were used to deal with that. This made swapping complicated, since it had to
be swapped back in to the same location.)

Which function of BALR are you enquiring about? The subroutine call part?


    > From: Angelo Papenhoff

    > The Whirlwind used the A register for this purpose. ...
    > Might be earlier than this, I just happen to know the Whirlwind
    > somewhat well. It's late 40s machine, so you probably won't find
    > anything *much* older.

The only machines older than Whirlwind I know of are the ACE (design;
not implemented until later) and EDVAC.

I have ACE stuff, but i) the documentation is really wierd, and hard to read,
and ii) it's really bizarre (it didn't have opcodes; different registers did
different things). There were subroutines written for it, but it's not clear
how they were called.

The EDVAC, the only thing I have on it is von Neumann's draft, and it's
even harder to read than Turing's ACE Report!

	Noel

             reply	other threads:[~2022-10-25 22:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-25 22:52 Noel Chiappa [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-10-12 19:01 [TUHS] " ron minnich
2022-10-24 23:46 ` [TUHS] " Angelo Papenhoff
2022-10-25  8:35   ` Angelo Papenhoff
2022-10-25 17:00     ` Lawrence Stewart
2022-10-25 18:26       ` Clem Cole
2022-10-25 20:05         ` Marc Donner
2022-10-25 21:03           ` Lawrence Stewart
2022-10-26  4:45       ` Ralph Corderoy
2022-10-26  5:29         ` Angelo Papenhoff
2022-10-26  7:52           ` Marc Donner
2022-10-26 11:12         ` Larry Stewart
2022-10-25 22:24 ` Bakul Shah
2022-10-25 22:41   ` Harald Arnesen
2022-10-25 22:47   ` Robert Clausecker

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=20221025225251.6FC1818C073@mercury.lcs.mit.edu \
    --to=jnc@mercury.lcs.mit.edu \
    --cc=tuhs@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).