[issue7201] double Endian problem and more on arm
report at bugs.python.org
Fri Sep 16 04:06:16 CEST 2011
Meador Inge <meadori at gmail.com> added the comment:
I think Mark's original pointer to issue1762561 was right on. The last
two cases are failing due to the mixed-endian format (mentioned
in that issue) used in OABI.
You can see this in the output of 'test_endian_double':
'182D4454FB210940' != 'FB210940182D4454'
Note that the values are the same except the two 32-bit words are
Similarly, in 'test_unaligned_native_struct_fields':
The first 8 bytes in each case are the same. The last 8 bytes of
each (which represent floating-point doubles) are the same except,
again, the words are swapped.
I am going to close this out as "won't fix". As mentioned in issue1762561, supporting OABI will involve taking on another
host platform. EABI is surely more predominant these days anyway.
resolution: -> wont fix
stage: -> committed/rejected
type: -> behavior
Python tracker <report at bugs.python.org>
More information about the Python-bugs-list