From: Doug Evans <dje@transmeta.com>
To: Ben Elliston <bje@redhat.com>
Cc: cgen development <cgen@sources.redhat.com>
Subject: Multiple ISAs for opcodes
Date: Sun, 12 Nov 2000 23:18:00 -0000 [thread overview]
Message-ID: <14863.38327.840899.856498@casey.transmeta.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0011131753150.29288-100000@moshpit.cygnus.com>
Ben Elliston writes:
> Hi,
>
> I posted a question to the list some weeks ago and received no responses of
> substance -- that surprises me. Rather than type my message again, here is
> a link to the archived original:
>
> http://sources.redhat.com/ml/cgen/2000-q4/msg00031.html
>
> So -- any thoughts?
This is new ground (albeit barely). What seems reasonable?
You could either have one enum that contains everything,
or you could generate two opc.h's, one for each ISA.
In and of itself, I prefer the latter.
next prev parent reply other threads:[~2000-11-12 23:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-12 22:57 Ben Elliston
2000-11-12 23:18 ` Doug Evans [this message]
2000-11-15 18:57 ` Ben Elliston
2000-11-13 4:01 ` Frank Ch. Eigler
-- strict thread matches above, loose matches on Subject: below --
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
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=14863.38327.840899.856498@casey.transmeta.com \
--to=dje@transmeta.com \
--cc=bje@redhat.com \
--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).