[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [pygame] Closing issue 211 with big-endian CPU test



On Sun, Oct 25, 2015 at 4:27 PM, Lenard Lindstrom <len-l@xxxxxxxxx> wrote:
Is there a need to continue big-endian support?
âBi-endian architectures are still around (ARM, MIPS in particular). AFAICT little endian won the war, but big endian is still around mainly for compatibility. The Raspberry Pi, for example, is almost universally configured to little endian, despite being a bi processor.

Also, notionally, programs could swap endian-ness when operating on certain memory regions for performance improvements. Though, I don't know of any modern programs that do that.
â
I mean, we leave in the big-endian specific code, but just leave it untested. Worry about it only if the need arises.
I like this solution. Making endianness go both ways with a compile flag isn't really extra effort.

Lenard Lindstrom
âIan