https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88739
--- Comment #18 from Segher Boessenkool <segher at gcc dot gnu.org> --- Well, it is always possible to generate code with the opposite endianness to what the hardware "wants". It just won't be very fast code. BITS_BIG_ENDIAN is just a convenience to the target code writer. The other four do matter, and are quite obvious really (and all four are necessary).
