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 cambridge dot redhat dot com>
Subject: Re: Endianness and CGEN_INT_INSN_P
From: Dave Brolley <brolley at redhat dot com>
Date: Tue, 02 Jan 2001 11:40:38 -0500
CC: cgen at sources dot redhat dot com
References: <Pine.LNX.4.21.0101021343260.19790-100000@host149.cambridge.redhat.com>

 From what I understand, CGEN_INT_INSN_P will not be true if there is at 
least one insn which will not fit into the word.

Dave

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.  Is this
> right?  If so, would it be better to restrict CGEN_INT_INSN_P to that
> case, or would it better to handle the multi-word case when
> CGEN_INT_INSN_P is true?
> 
> Richard
> 
> 
> 
> 
>

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

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]