From: Paul Winalski <paul.winalski@gmail.com>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Cc: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] Unix quix
Date: Fri, 24 Jan 2020 13:57:05 -0500 [thread overview]
Message-ID: <CABH=_VQPqv90fywr3Dj-CDyyA9QjnCg0pASHeS_HO_6bouH+XQ@mail.gmail.com> (raw)
In-Reply-To: <20200122184244.14CBB18C083@mercury.lcs.mit.edu>
On 1/22/20, Noel Chiappa <jnc@mercury.lcs.mit.edu> wrote:
>
> Pretty interesting machine, if you study its instruction set, BTW; with no
> stack, subroutines are 'interesting'.
The IBM S/360/370 operating systems such as DOS/360 and DOS/VS didn't
use a stack, either, unless you were doing recursion. When we got our
VAX, I was puzzled as to why they would throw away an entire register
just to point at a stack.
-Paul W.
next prev parent reply other threads:[~2020-01-24 18:57 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-22 18:42 Noel Chiappa
2020-01-24 18:57 ` Paul Winalski [this message]
2020-01-30 4:00 ` Dave Horsfall
2020-01-30 6:32 ` Angelo Papenhoff
-- strict thread matches above, loose matches on Subject: below --
2020-01-24 19:38 Nelson H. F. Beebe
2020-01-24 20:05 ` Bakul Shah
2020-01-22 20:49 Doug McIlroy
2020-01-22 23:06 ` Rob Pike
2020-01-23 15:56 ` Leah Neukirchen
2020-01-24 2:44 ` Warner Losh
2020-01-24 14:49 ` Clem Cole
2020-01-24 16:34 ` Jon Steinhart
2020-01-26 0:03 ` Heinz Lycklama
2020-01-24 16:40 ` Warner Losh
2020-01-20 20:28 Rob Pike
2020-01-20 21:06 ` Adam Thornton
2020-01-22 9:31 ` Rob Pike
2020-01-22 14:57 ` Dan Cross
2020-01-22 17:54 ` Warner Losh
2020-01-22 18:01 ` Vincenzo Nicosia
2020-01-22 18:21 ` Clem Cole
2020-01-22 19:42 ` Warner Losh
2020-01-22 20:42 ` Clem Cole
2020-01-22 23:10 ` Rob Pike
2020-01-22 23:34 ` Warner Losh
2020-01-22 23:42 ` Clem Cole
2020-01-22 19:00 ` Warner Losh
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='CABH=_VQPqv90fywr3Dj-CDyyA9QjnCg0pASHeS_HO_6bouH+XQ@mail.gmail.com' \
--to=paul.winalski@gmail.com \
--cc=jnc@mercury.lcs.mit.edu \
--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).