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]

Endianness and CGEN_INT_INSN_P



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



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