From: Doug Evans <dje@transmeta.com>
To: Greg McGary <greg@mcgary.org>
Cc: "Frank Ch. Eigler" <fche@redhat.com>, cgen@sourceware.cygnus.com
Subject: Re: defining 2-operand version of 3-operand insns?
Date: Wed, 06 Dec 2000 10:45:00 -0000 [thread overview]
Message-ID: <14894.35112.39862.784263@casey.transmeta.com> (raw)
In-Reply-To: <msg0k1wfzh.fsf@mcgary.org>
Greg McGary writes:
> Doug, does that sound reasonable to you, or are you philosophically
> opposed to the entire 2/3 operand insn hack?
Could I see the .cpu file in question so I have a clear understanding
of what the problems and issues are and so that I can play with them
myself?
[at this point I don't have enough info to form an opinion]
next prev parent reply other threads:[~2000-12-06 10:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-01 14:17 Greg McGary
2000-12-01 14:33 ` Frank Ch. Eigler
2000-12-01 15:55 ` Greg McGary
2000-12-06 10:29 ` Greg McGary
2000-12-06 10:40 ` Greg McGary
2000-12-06 10:45 ` Doug Evans [this message]
2000-12-06 10:42 ` Frank Ch. Eigler
2000-12-06 11:13 ` Doug Evans
2000-12-06 11:26 ` Frank Ch. Eigler
2000-12-06 11:51 ` Doug Evans
2000-12-06 11:40 ` Greg McGary
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=14894.35112.39862.784263@casey.transmeta.com \
--to=dje@transmeta.com \
--cc=cgen@sourceware.cygnus.com \
--cc=fche@redhat.com \
--cc=greg@mcgary.org \
/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).