On Thu, Nov 09, 2017 at 07:16:52AM +0100, Luc Van Oostenryck wrote: > sparc is big-endian only but sparse assumes the same endianness > as the building machine. > This is problematic for code which expect __BYTE_ORDER__ being > correctly predefined by the compiler which sparse can then > pre-process differently from what gcc would, depending on the > building machine endianness. > > Fix this by letting sparse know about the architecture endianness. You're posted patches for this for about half a dozen architectures now, but we also now have generic Kconfig symbols for the byte order. I'd much rather see this done in generic code than hacking it up everywhere. -- To unsubscribe from this list: send the line "unsubscribe sparclinux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
