From: toby@telegraphics.com.au (Toby Thain)
Subject: [TUHS] Subroutine calling conventions - was Re: Happy birthday, PDP-8!
Date: Mon, 27 Mar 2017 09:45:37 -0400 [thread overview]
Message-ID: <d56f9c9f-f1b7-50ff-1121-9e004cd8177d@telegraphics.com.au> (raw)
In-Reply-To: <20170327003105.B535018C085@mercury.lcs.mit.edu>
On 2017-03-26 8:31 PM, Noel Chiappa wrote:
> > From: Dave Horsfall
>
> > And as for subroutine calls on the -8, let's not go there... As I dimly
> > recall, it planted the return address into the first word of the called
> > routine and jumped to the second instruction; to return, you did an
> > indirect jump to the first word.
>
> That do be correct.
>
> That style of subroutine call goes back a _long_ way. IIRC, Whirlwind used
> that kind of linkage (alas, I've misplaced my copy of the Whirlwind
> instruction manual, sigh - a real tresure).
This link arrived in my twitter feed this morning.
https://people.cs.clemson.edu/~mark/subroutines.html
--T
>
> ISTVR there was something about the way Whirlwind did it that made it clear
> how it came to be the way it was - IIRC, the last instruction in the
> subroutine was normally a 'jump to literal' (i.e. a constant, in the
> instruction), and the Whirlwind 'jump to subroutine' stored the return address
> in a register; there was a special instruction (normally the first one in any
> subroutine) that stored the low-order N bits of that register in the literal
> field of the last instruction: i.e. self-modifying code.
>
> The PDP-6 (of which the PDP-10 was a clone) was on the border of that period;
> it had both types of subroutine linkage (store the return in the destination,
> and jump to dest+1; and also push the return on the stack).
>
> Noel
>
prev parent reply other threads:[~2017-03-27 13:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-27 0:31 [TUHS] " Noel Chiappa
2017-03-27 0:37 ` Arthur Krewat
2017-03-27 12:05 ` Tim Bradshaw
2017-03-27 13:35 ` Tony Finch
2017-03-27 21:37 ` Terry Smith
2017-03-27 13:45 ` Toby Thain [this message]
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=d56f9c9f-f1b7-50ff-1121-9e004cd8177d@telegraphics.com.au \
--to=toby@telegraphics.com.au \
/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).