From: iking@microsoft.com (Ian King)
Subject: [pups] Bringing up the fist C compiler
Date: Thu, 5 Sep 2002 08:36:48 -0700 [thread overview]
Message-ID: <8D25F244B8274141B5D313CA4823F39C057A2389@red-msg-06.redmond.corp.microsoft.com> (raw)
About a thousand years ago, I recall hand-building programs for 8-bit microprocessors (in what we'd call embedded systems today). In many cases, I was the "assembler", writing directly in machine code which was then either keyed in through front-panel switches or burned into a PROM.... -- Ian
-----Original Message-----
From: Johnny Billquist [mailto:bqt at update.uu.se]
Sent: Thu 9/5/2002 5:05 AM
To: Tim Bradshaw
Cc: pups at minnie.tuhs.org
Subject: Re: [pups] Bringing up the fist C compiler
On Thu, 5 Sep 2002, Tim Bradshaw wrote:
> * Johnny Billquist wrote:
>
> > How? It was written, of course. In assembler. By that time, you already
> > had the assembler, an editor, and other commonly used system programs, so
> > it's just a case of the normal development cycle.
>
> Is this known or is it deduction?
[...]
Ah. Ok, now I understand what you're asking for.
You want to know what the first C was written in, and what that
compiler/assembler was written in/on, and so on...
No, I'm just deducting. Since the reference posted said that TMG was the
first higher level language implemented, it follows that it must have been
written in a low level language, namely assembler.
Admittedly, the PDP-7 TMG *could* have been written in some high level
language on some other machine using some tool that made a PDP-7
executable, so your guess is as good as mine.
But even though I cannot account for all steps, I can guarantee that at
the end of the chain, you *will* find assembler.
I guess my MACRO-11 implementation of C isn't good enough. :-)
(Well, it ain't mine, it's the normal DECUS C, but I'm hacked some at it.)
Johnny
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at update.uu.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
_______________________________________________
PUPS mailing list
PUPS at minnie.tuhs.org
http://minnie.tuhs.org/mailman/listinfo/pups
next reply other threads:[~2002-09-05 15:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-05 15:36 Ian King [this message]
-- strict thread matches above, loose matches on Subject: below --
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
2002-09-05 22:54 [pups] Bringing " Carl Lowenstein
2002-09-05 17:47 Al Kossow
2002-09-05 23:21 ` Johnny Billquist
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
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=8D25F244B8274141B5D313CA4823F39C057A2389@red-msg-06.redmond.corp.microsoft.com \
--to=iking@microsoft.com \
/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).