From: Doug Evans <dje@google.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: cgen@sourceware.org
Subject: Re: CGEN_WIDE_INT_INSN_P?
Date: Sat, 26 Sep 2009 02:50:00 -0000 [thread overview]
Message-ID: <e394668d0909251950u6abe3665l3d55c7844111cf61@mail.gmail.com> (raw)
In-Reply-To: <20090926013727.GI27227@redhat.com>
On Fri, Sep 25, 2009 at 6:37 PM, Frank Ch. Eigler <fche@redhat.com> wrote:
> 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.
No disagreement there. My only intention was to give enough to
present the flavor of the change (once that's done the rest readily
presents itself for inspection :-)).
prev parent reply other threads:[~2009-09-26 2:50 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 ` CGEN_WIDE_INT_INSN_P? Frank Ch. Eigler
2009-09-26 2: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=e394668d0909251950u6abe3665l3d55c7844111cf61@mail.gmail.com \
--to=dje@google.com \
--cc=cgen@sourceware.org \
--cc=fche@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).