This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: CPP macro for Byte-order


Richard Earnshaw <rearnsha@arm.com> writes:

| > 
| > On the other hand, the gcc backends define BITS_BIG_ENDIAN,
| > BYTES_BIG_ENDIAN, and WORDS_BIG_ENDIAN (you would want BYTES_BIG_ENDIAN to
| > solve the problem of detecting NaNs and the like). 
| 
| It is a common mistake to confuse the INTEGER endian settings with the 
| requirements for floating point numbers.  The two need not be related, and 
| on many architectures aren't.
| 
| Please keep these separate.

I understand the conceptual difference with the two.  But _concretely_
are there supported plateforms where they do actually differ?  What
are your suggestions?

-- Gaby
CodeSourcery, LLC                       http://www.codesourcery.com


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