From: Ben Elliston <bje@redhat.com>
To: Doug Evans <dje@transmeta.com>
Cc: <cgen@sources.redhat.com>
Subject: Re: Multiple ISAs for opcodes
Date: Wed, 15 Nov 2000 19:08:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.30.0011161406140.9071-100000@moshpit.cygnus.com> (raw)
In-Reply-To: <14826.26832.863861.836565@casey.transmeta.com>
For the sake of discussion, is this something akin to arm vs thumb?
Yes. Here's my analysis of the situtation:
* fields, operands, instructions are deliniated by the isa
in my port (just like arm,thumb).
* a pair of the opcodes files need to be completely generated down
this axis, modulo things in common -- but what are they?
What's a good way to proceed?
Ben
next prev parent reply other threads:[~2000-11-15 19:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-15 17:44 Ben Elliston
2000-10-15 19:34 ` Doug Evans
2000-10-15 19:40 ` Ben Elliston
2000-11-15 19:08 ` Ben Elliston [this message]
2000-11-12 22:57 Ben Elliston
2000-11-12 23:18 ` Doug Evans
2000-11-15 18:57 ` Ben Elliston
2000-11-13 4:01 ` Frank Ch. Eigler
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=Pine.LNX.4.30.0011161406140.9071-100000@moshpit.cygnus.com \
--to=bje@redhat.com \
--cc=cgen@sources.redhat.com \
--cc=dje@transmeta.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).