From: Doug Evans <dje@transmeta.com>
To: fche@redhat.com (Frank Ch. Eigler)
Cc: Stan Cox <scox@redhat.com>, cgen@sourceware.cygnus.com
Subject: Re: patch for insn size > word size
Date: Thu, 05 Apr 2001 22:31:00 -0000 [thread overview]
Message-ID: <15053.21656.602535.619823@casey.transmeta.com> (raw)
In-Reply-To: <o5r8z8v2n4.fsf@toenail.toronto.redhat.com>
Frank Ch. Eigler writes:
> : > This proposed patch adds support for architectures where the insn size
> : > is larger than the word size. [...]
> :
> : I'd like to think about this one for a day or two.
>
> We have a need to take this whole opcodes area of the cgen runtime a
> leap beyond where it is now. Support for variable and strange length
> instruction sets all have increasing urgency. I am tempted to finally
> reorganize/rewrite this area to use a single consistent general
> system.
I'd prefer to see a proposal _first_!
prev parent reply other threads:[~2001-04-05 22:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-04 9:01 Stan Cox
2001-04-04 11:06 ` Doug Evans
[not found] ` <15051.25210.786209.678294.cygnus.local.cgen@casey.transmeta.com>
2001-04-04 13:20 ` Frank Ch. Eigler
2001-04-05 22:31 ` 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=15053.21656.602535.619823@casey.transmeta.com \
--to=dje@transmeta.com \
--cc=cgen@sourceware.cygnus.com \
--cc=fche@redhat.com \
--cc=scox@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).