The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: peter.jeremy@alcatel.com.au (Peter Jeremy)
Subject: [pups] Bringing up the fist C compiler
Date: Tue, 10 Sep 2002 07:17:10 +1000	[thread overview]
Message-ID: <20020909211710.GA87874@gsmx07.alcatel.com.au> (raw)
In-Reply-To: <3D77823A.1050504@pacbell.net>

On 2002-Sep-05 09:11:38 -0700, Michael Davidson <MichaelDavidson at pacbell.net> wrote:
>Johnny Billquist wrote:
>>But even though I cannot account for all steps, I can guarantee that at
>>the end of the chain, you *will* find assembler.
>
>Or, just possibly, Alan Turing hand punching Mark 1 machine code onto
>paper tape ;-)

Actually, to use one of the other "first stored-program computer"
candidates, EDSAC provided what I consider to be a very sophisticated
assembler/loader that read programs off paper tape into memory.  This
assembler/loader ("initial orders") was 41 instructions long and was
hard-wired onto uniselectors which were automatically loaded into
memory when the start switch was pressed.

It supported:
- single-letter mnemonics for each of the 18 instructions
- decimal entry of numbers (EDSAC was binary internally)
- 13 single-letter variables which could be assigned or added to the
  address in each instruction.
- program relocation (courtesy of the above)

Overall, the input language looks much closer to assembler language
than the instruction bit patterns in memory.  (The Mathematical
Laboratory also developed an extensive collection of reusable
subroutines intended to simplify program development).

Ref: "The Preparation of Programs for an Electronic Digital Computer",
   M.V. Wilkes, D.J. Wheeler, S. Gill, Addison-Wesley, 1951.

A rummage around on the WEB will turn up a couple of EDSAC simulators
and sample programs.

Peter



  reply	other threads:[~2002-09-09 21:17 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-05  8:06 Tim Bradshaw
2002-09-05  8:16 ` Warren Toomey
2002-09-05  9:38 ` Johnny Billquist
2002-09-05  9:41   ` Tim Bradshaw
2002-09-05 10:07     ` Johnny Billquist
2002-09-05 10:15       ` Lars Brinkhoff
2002-09-05 11:19       ` Tim Bradshaw
2002-09-05 12:05         ` Johnny Billquist
2002-09-05 16:11           ` Michael Davidson
2002-09-09 21:17             ` Peter Jeremy [this message]
2002-09-05 15:36 Ian King
2002-09-05 17:47 Al Kossow
2002-09-05 23:21 ` Johnny Billquist
2002-09-05 22:54 Carl Lowenstein
2002-09-06  5:35 [pups] bringing " Dennis Ritchie
2002-09-06  8:14 ` Warren Toomey
2002-09-06  8:56   ` Lars Brinkhoff
2002-09-06 10:28     ` Warren Toomey
2002-09-06 10:52       ` Lars Brinkhoff
2002-09-06 11:06         ` Warren Toomey
2002-09-06  8:28 ` Lars Brinkhoff

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=20020909211710.GA87874@gsmx07.alcatel.com.au \
    --to=peter.jeremy@alcatel.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).