Return to Answer

deleted 8 characters in body

Source Link

edited May 6, 2016 at 2:35

35.2k
13
134
238

You have to use predefined compiler macros (_BIG_ENDIAN_\__BIG_ENDIAN__ or _LITTLE_ENDIAN_\__LITTLE_ENDIAN__ with clang, or _BYTE_ORDER_\__BYTE_ORDER__ with gcc).

The other compiler macro tricks mentioned will only detect the endianness of the architecture you are compiling onon, not the endianness of the architecture you are compiling forfor, so something like this is wrong wrong:

#define IS_BIG_ENDIAN ('\x01\x02\x03\x04' == 0x01020304)

\#define IS_BIG_ENDIAN ('\x01\x02\x03\x04' == 0x01020304)

You have to use predefined compiler macros (_BIG_ENDIAN_ or _LITTLE_ENDIAN_ with clang, or _BYTE_ORDER_ with gcc)

The other compiler macro tricks mentioned will only detect the endianness of the architecture you are compiling on, not the endianness of the architecture you are compiling for, so something like this is wrong :

#define IS_BIG_ENDIAN ('\x01\x02\x03\x04' == 0x01020304)

You have to use predefined compiler macros (\__BIG_ENDIAN__ or \__LITTLE_ENDIAN__ with clang, or \__BYTE_ORDER__ with gcc).

The other compiler macro tricks mentioned will only detect the endianness of the architecture you are compiling on, not the endianness of the architecture you are compiling for, so something like this is wrong:

\#define IS_BIG_ENDIAN ('\x01\x02\x03\x04' == 0x01020304)

Source Link

answered May 5, 2016 at 22:15

ajv

You have to use predefined compiler macros (_BIG_ENDIAN_ or _LITTLE_ENDIAN_ with clang, or _BYTE_ORDER_ with gcc)

#define IS_BIG_ENDIAN ('\x01\x02\x03\x04' == 0x01020304)