From: fche@redhat.com (Frank Ch. Eigler)
To: apl@alum.mit.edu
Cc: cgen@sourceware.cygnus.com
Subject: Re: problems simulating register-only architecture...
Date: Thu, 24 May 2001 16:04:00 -0000 [thread overview]
Message-ID: <o566eqe4dg.fsf@touchme.toronto.redhat.com> (raw)
In-Reply-To: <200105242031.QAA10298.cygnus.local.cgen@iron>
lehotsky wrote:
: The machine I'm developing a simulator for is a "register only"
: architecture, whose only memory is 512, 32-bit registers.
: [...]
: There are 4 registers that are "special", in that
: they are auto-indexed (e.g.) reading register X uses the contents of
: register Y as an indirect register number.
: [...]
This stuff is tricky; some cgen features don't compose well.
I'd advise keeping it simple: use c-call to hook to a single C
getter-setter function pair, and hide the indirection within. (BTW,
don't bother represent the actual RAM block (h-memory) within cgen.)
- FChE
next parent reply other threads:[~2001-05-24 16:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200105242031.QAA10298.cygnus.local.cgen@iron>
2001-05-24 16:04 ` Frank Ch. Eigler [this message]
2001-05-24 16:23 ` Alan Lehotsky
2001-05-24 16:25 ` Frank Ch. Eigler
2001-05-24 13:39 lehotsky
2001-05-24 15:35 ` Ben Elliston
2001-05-24 16:18 ` Alan Lehotsky
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=o566eqe4dg.fsf@touchme.toronto.redhat.com \
--to=fche@redhat.com \
--cc=apl@alum.mit.edu \
--cc=cgen@sourceware.cygnus.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 read-only IMAP folder(s) and NNTP newsgroup(s).