From: Doug Evans <dje@transmeta.com>
To: Michael Meissner <cgen-mail@the-meissners.org>
Cc: cgen@sources.redhat.com
Subject: Types and other issues with cgen
Date: Wed, 06 Aug 2003 20:50:00 -0000 [thread overview]
Message-ID: <16177.18314.104243.96490@casey.transmeta.com> (raw)
In-Reply-To: <16177.14973.213564.499122@casey.transmeta.com>
Doug Evans writes:
> > Michael writes
> > 2) Cgen has a type mechanism (DI/SI/etc.) but it doesn't seem to be used in the
> > actual code for at least the assembler and disassembler
>
> Using the modes in the assembler/disassembler isn't the right way to go.
> These modes are for semantic operation, not assembly/disassembly.
> Imagine some instruction with an immediate operand that is a fixed
> set of constants that is encoded with special magic numbers.
> Register indices are another example.
> There's a disconnect between representation in the instruction
> and use during semantic evaluation.
Blech. I should have let my reply sit in my head awhile before
^c^c-ing.
Here's my proposal. We record in cgen_fields a type big enough
to hold the field (or some minor variant thereof) and have
inserters/extractors for each type in use.
prev parent reply other threads:[~2003-08-06 18:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-06 17:27 Michael Meissner
2003-08-06 17:47 ` Doug Evans
2003-08-06 18:23 ` Michael Meissner
2003-08-06 20:50 ` Doug Evans [this message]
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=16177.18314.104243.96490@casey.transmeta.com \
--to=dje@transmeta.com \
--cc=cgen-mail@the-meissners.org \
--cc=cgen@sources.redhat.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).