The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: John Cowan <cowan@ccil.org>
To: Doug McIlroy <doug@cs.dartmouth.edu>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Memory management in Dennis Ritchie's C Compiler
Date: Wed, 26 Aug 2020 11:41:21 -0400	[thread overview]
Message-ID: <CAD2gp_R84MDhSs4KEGv0zi3Pm+Or16gCY934oNbbS4Njtzhuyg@mail.gmail.com> (raw)
In-Reply-To: <202008261324.07QDOxln046419@tahoe.cs.Dartmouth.EDU>

[-- Attachment #1: Type: text/plain, Size: 1344 bytes --]

On Wed, Aug 26, 2020 at 9:25 AM Doug McIlroy <doug@cs.dartmouth.edu> wrote:

I hadn't heard this urban legend before. A stack is certainly
> manageable without auto-increment/decrement (AID) instructions.


Absolutely.  I should have qualified my remarks by saying "when writing in
assembly language", which was the universal language of all PDP-11
operating systems until Unix.  VMS adopted Bliss (which is what C would be
like if it had come to us through a different dharma line[*]) as its
principal implementation language.


> But when the stack contains
> local variables that are accessed multiple times, the accesses
> are offset from the stack pointer.


Or the frame pointer, which has the advantage that the callee can push
arbitrary stuff on the stack without having to explicitly account for it
later, and the disadvantage that it ties up yet another register when they
are in short supply.

[*] Don't laugh too hard: you yourself have already been mythologized in
precisely this fashion.  See <
http://www.catb.org/~esr/writings/unix-koans/two_paths.html> and <
http://www.catb.org/~esr/writings/unix-koans/zealot.html>.



John Cowan          http://vrici.lojban.org/~cowan        cowan@ccil.org
Mark Twain on Cecil Rhodes: I admire him, I freely admit it,
and when his time comes I shall buy a piece of the rope for a keepsake.

[-- Attachment #2: Type: text/html, Size: 2281 bytes --]

  reply	other threads:[~2020-08-26 15:42 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-26 13:24 Doug McIlroy
2020-08-26 15:41 ` John Cowan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-08-27  8:37 Paul Ruizendaal
2020-08-26 15:59 Noel Chiappa
2020-08-26 16:09 ` Warner Losh
2020-08-26 19:13   ` Clem Cole
2020-08-26 16:14 ` Jim Geist
2020-08-26 17:31 ` John Cowan
2020-08-25  9:36 Steve Simon
2020-08-17 22:32 Norman Wilson
2020-08-17 22:55 ` Bakul Shah
2020-08-17 23:12 ` Chet Ramey
2020-08-18  6:33 ` arnold
2020-08-17 19:51 Noel Chiappa
2020-08-17 19:27 Noel Chiappa
2020-08-17 19:30 ` Larry McVoy
2020-08-17 19:44   ` Dan Halbert
2020-08-17 19:50   ` Paul Winalski
2020-08-17 22:05     ` Arthur Krewat
2020-08-18  0:52 ` Rob Gingell
2020-08-17  2:02 Noel Chiappa
2020-08-17 18:02 ` Paul Winalski
2020-08-17 18:13   ` Jim Geist
2020-08-17 18:48     ` Paul Winalski
2020-08-17 19:08       ` Jim Geist
2020-08-17 19:28         ` Paul Winalski
2020-08-17 19:35           ` Jim Geist
2020-08-17 19:41             ` Richard Salz
2020-08-17 23:40               ` Steffen Nurpmeso
2020-08-15 21:50 Dibyendu Majumdar
2020-08-16 15:20 ` arnold
2020-08-16 15:27   ` Jim Geist
2020-08-17 16:13 ` Dan Cross
2020-08-17 20:16   ` Dibyendu Majumdar
2020-08-17 20:34     ` Paul Winalski
2020-08-17 20:43       ` Dibyendu Majumdar
2020-08-17 21:05         ` Warner Losh
2020-08-17 22:47         ` Dave Horsfall
2020-08-17 23:06           ` Nemo Nusquam
2020-08-17 21:29     ` Dibyendu Majumdar
2020-08-24 15:58     ` Dan Cross
2020-08-24 17:08       ` John Cowan
2020-08-24 17:15         ` Clem Cole
2020-08-24 17:24           ` Clem Cole
2020-08-24 17:20         ` Dan Cross
2020-08-25 23:06           ` Arthur Krewat

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=CAD2gp_R84MDhSs4KEGv0zi3Pm+Or16gCY934oNbbS4Njtzhuyg@mail.gmail.com \
    --to=cowan@ccil.org \
    --cc=doug@cs.dartmouth.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).