Bytes order and words order

[Gabriel Dos Reis]

Neil Booth <neil@daikokuya.co.uk> writes:

| Gabriel Dos Reis wrote:-
| 
| > | #define __LITTLE_ENDIAN 1234
| > | #define __BIG_ENDIAN    4321
| > | 
| > | and some other system may well have such definitions with trailing __.
| > 
| > You're right.  I just posted a message asking what y'all think about
| > 
| >     __GCC_LITTLE_ENDIAN__
| 
| Ah, OK.  That's fine with me.  That's the target version, yes?  What
| would the host / build ones be?


Sorry I was unclear.  

What I meant is this:  The symbols (and their values)
__GCC_LITTE_ENDIAN__ and __GCC_BIG_ENDIAN__ are "universal".

Now, I would like define

   __TARGET_FLOAT_BYTES_ORDER__
   __TARGET_FLOAT_WORDS_ORDER__

   ...

with values in {__GCC_LITTE_ENDIAN__, __GCC_BIG_ENDIAN__}.

-- Gaby