[issue7201] double Endian problem and more on arm

2011-09-16 Thread Mark Dickinson
Mark Dickinson dicki...@gmail.com added the comment: won't fix seems reasonable to me. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7201 ___

[issue7201] double Endian problem and more on arm

2011-09-16 Thread Mark Dickinson
Changes by Mark Dickinson dicki...@gmail.com: -- status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7201 ___ ___ Python-bugs-list

[issue7201] double Endian problem and more on arm

2011-09-15 Thread Meador Inge
Meador Inge mead...@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' !=

[issue7201] double Endian problem and more on arm

2011-09-14 Thread Meador Inge
Meador Inge mead...@gmail.com added the comment: OK, I got an OABI system setup. I am seeing the 'test_struct_return_2H' failure, which actually segfaults in my setup. The difference does, indeed, seem like an ABI mismatch. The test code that is failing has a Python side like: def

[issue7201] double Endian problem and more on arm

2011-09-14 Thread Meador Inge
Meador Inge mead...@gmail.com added the comment: The 'test_endian_double' test fails because the 'double' floating-point type for an interpreter built for OABI is unknown: float.__getformat__(float) 'IEEE, little-endian' float.__getformat__(double) 'unknown' According to [1], the double

[issue7201] double Endian problem and more on arm

2011-09-13 Thread Mark Dickinson
Mark Dickinson dicki...@gmail.com added the comment: I don't think it is practical to support both ABIs. I suspect you're right. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7201 ___

[issue7201] double Endian problem and more on arm

2011-09-12 Thread Mark Dickinson
Mark Dickinson dicki...@gmail.com added the comment: I ran the ctypes tests on Debian GNU/Linux 5.0.8 (lenny) on an ARMv5tejl Versatile kernel and everything passed. I believe the problem is specific to machines still using the old ABI ('OABI'). Which ABI was being used on your test

[issue7201] double Endian problem and more on arm

2011-09-12 Thread Meador Inge
Meador Inge mead...@gmail.com added the comment: On Mon, Sep 12, 2011 at 7:10 AM, Mark Dickinson rep...@bugs.python.org wrote: Mark Dickinson dicki...@gmail.com added the comment: I believe the problem is specific to machines still using the old ABI ('OABI').  Which ABI was being used on

[issue7201] double Endian problem and more on arm

2011-09-11 Thread Meador Inge
Meador Inge mead...@gmail.com added the comment: I ran the ctypes tests on Debian GNU/Linux 5.0.8 (lenny) on an ARMv5tejl Versatile kernel and everything passed. Is anyone else still seeing errors? -- assignee: theller - nosy: +meadori -theller

[issue7201] double Endian problem and more on arm

2009-10-25 Thread Mark Dickinson
Mark Dickinson dicki...@gmail.com added the comment: The 4th failure (test_endian_double) probably has nothing to do with ctypes. See also issue #1762561. -- nosy: +mark.dickinson ___ Python tracker rep...@bugs.python.org

[issue7201] double Endian problem and more on arm

2009-10-25 Thread Mancausoft
Mancausoft b...@mancausoft.org added the comment: Mark Dickinson rep...@bugs.python.org scrisse: The 4th failure (test_endian_double) probably has nothing to do with ctypes. See also issue #1762561. I try to use the patch arm-float2.diff, but test result is the same:

[issue7201] double Endian problem and more on arm

2009-10-25 Thread Mark Dickinson
Mark Dickinson dicki...@gmail.com added the comment: Hmm. Okay, I take it back then. :) Sorry for the noise. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7201 ___

[issue7201] double Endian problem and more on arm

2009-10-24 Thread Mancausoft
New submission from Mancausoft b...@mancausoft.org: I compile python for arm (on debian etch) but it don't pass ctype test: == FAIL: test_struct_return_2H (ctypes.test.test_as_parameter.AsParamPropertyWrapperTestCase)