From: "Frank Ch. Eigler" <fche@redhat.com>
To: Doug Evans <dje@google.com>
Cc: cgen@sourceware.org
Subject: Re: CGEN_WIDE_INT_INSN_P?
Date: Sat, 26 Sep 2009 01:37:00 -0000 [thread overview]
Message-ID: <20090926013727.GI27227@redhat.com> (raw)
In-Reply-To: <20090926005044.1E975843AC@ruffy.mtv.corp.google.com>
Hi -
On Fri, Sep 25, 2009 at 05:50:44PM -0700, Doug Evans wrote:
> On the opcodes-like size of things,
> I remember ages ago talk of not having a choice between representing
> instructions as an int or as a byte stream,
> and just having a byte stream.
>
> I kinda like using an int for targets where it feels like the
> obvious choice (e.g. sparc, etc.).
> Wrappers could fold CGEN_INT_INSN_P targets into byte streams.
> [...]
The hard part seems to be not the representation typedefs, but the
operations thereupon. Fetching, masking, printing, comparing,
constitute a little API that hand-written (e.g. simulator) code
needs to be aware of, and perhaps flexible with regards to.
- FChE
next prev parent reply other threads:[~2009-09-26 1:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-26 0:50 CGEN_WIDE_INT_INSN_P? Doug Evans
2009-09-26 1:37 ` Frank Ch. Eigler [this message]
2009-09-26 2:50 ` CGEN_WIDE_INT_INSN_P? Doug Evans
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=20090926013727.GI27227@redhat.com \
--to=fche@redhat.com \
--cc=cgen@sourceware.org \
--cc=dje@google.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).