This is the mail archive of the cgen@sources.redhat.com mailing list for the CGEN project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]

Re: Endianness and CGEN_INT_INSN_P

To: Richard Sandiford <rsandifo at redhat dot com>
Subject: Re: Endianness and CGEN_INT_INSN_P
From: "Frank Ch. Eigler" <fche at redhat dot com>
Date: Tue, 2 Jan 2001 11:48:52 -0500
Cc: cgen at sources dot redhat dot com
References: <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

PGP signature

Follow-Ups:
- Re: Endianness and CGEN_INT_INSN_P
  - From: Doug Evans

References:
- Endianness and CGEN_INT_INSN_P
  - From: Richard Sandiford

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]