From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Subject: [TUHS] pdp-11 assembly as a hll?
Date: Wed, 14 Feb 2018 08:15:04 -0500 (EST) [thread overview]
Message-ID: <20180214131504.2DBD418C095@mercury.lcs.mit.edu> (raw)
> From: Dave Horsfall <dave at horsfall.org>
> I'd like to see it handle "JSR PC,@(SP)+"...
Heh!
But that does point out that the general concept is kind of confused - at
least, if you hope to get a fully working program out the far end. The only
way to do that is build (effectively) a simulator, one that _exactly_
re-creates the effects on the memory and registers of the original program.
Only instead of reading binary machine code, this one's going to read in the
machine language source, and produce a custom simulator, one that can run only
one program - the one fed into it.
Think of it as a 'simulator compiler'! :-)
Noel
next reply other threads:[~2018-02-14 13:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-14 13:15 Noel Chiappa [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-02-14 8:41 Paul Ruizendaal
2018-02-14 1:08 Warner Losh
2018-02-14 3:18 ` Dave Horsfall
2018-02-14 5:12 ` Warner Losh
2018-02-14 6:43 ` Dave Horsfall
2018-02-14 7:27 ` Bakul Shah
2018-02-14 7:28 ` Ian Zimmerman
2018-02-14 16:03 ` Paul Winalski
2018-02-14 16:56 ` 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=20180214131504.2DBD418C095@mercury.lcs.mit.edu \
--to=jnc@mercury.lcs.mit.edu \
/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).