From: "Frank Ch. Eigler" <fche@redhat.com>
To: Richard Sandiford <rsandifo@redhat.com>
Cc: cgen@sources.redhat.com
Subject: Re: Endianness and CGEN_INT_INSN_P
Date: Tue, 02 Jan 2001 08:49:00 -0000 [thread overview]
Message-ID: <20010102114852.D19510@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0101021343260.19790-100000@host149.cambridge.redhat.com>
Hi -
On Tue, Jan 02, 2001 at 01:48:37PM +0000, Richard Sandiford wrote:
: When CGEN_INT_INSN_P is true, the instruction gets written as a single
: integer with the bytes arranged according to the target endianness. This
: only seems appropriate when every instruction is one word long.
The code checks for all instructions being at most one word (32 bits)
long, not exactly one word long.
I must admit that I would prefer to see a single general mechanism
(byte strings) as opposed to that PLUS a reasonable but tricky
optimization. Doug, do you have any sense of how much processing
time the INT_INSN_P flag saves when present?
- FChE
--
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE6UgZ0VZbdDOm/ZT0RAvRIAJ9J9hv+EnaUZScnXmVfc2GBnbvPpQCbBGCe
rAT/dyavD0kGFVZXJP7uupo=
=L/4H
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2001-01-02 8:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-02 5:48 Richard Sandiford
2001-01-02 8:38 ` Dave Brolley
2001-01-02 9:21 ` Doug Evans
2001-01-02 9:21 ` Richard Sandiford
2001-01-02 8:49 ` Frank Ch. Eigler [this message]
2001-01-02 9:39 ` Doug Evans
2001-01-02 14:10 ` 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=20010102114852.D19510@redhat.com \
--to=fche@redhat.com \
--cc=cgen@sources.redhat.com \
--cc=rsandifo@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).