Frank Schaefer added the comment:
Well, after perusing the ctypes callproc.c code, I found the hacks referenced
by martin.panter and tried activating them with some SPARC64 #ifdefs:
--- python3.6-3.6.6.orig/Modules/_ctypes/callproc.c
+++ python3.6-3.6.6/Modules/_ctypes/callproc.c
@@ -1041,6
Frank Schaefer added the comment:
FYI the libffi bug report is open here:
https://github.com/libffi/libffi/issues/451
As noted in the bug report, this issue actually doesn't appear to impact ARM64
(or ARM32 GNUEABI/GNUEABIHF).
--
___
Python
Martin Panter added the comment:
Seems to be a common theme on various 64-bit ABIs. There is already a fix for
Python’s Windows copy of the FFI library (Issue 29565), and a “hack” for Arm
and x86 Windows (again!): Issue 30353.
--
nosy: +martin.panter
Frank Schaefer added the comment:
Further details:
I cloned libffi from a few days ago to see if I had any different behavior. So
far the test fails the same way with the updated libffi.
I'll also see about contacting libffi upstream and see what they can suggest
here.
--
New submission from Frank Schaefer :
Python 3.6.6 on Linux 4.16.18 SPARC64 fails test_ctypes. Specifically, it
appears to be due to the _testfunc_large_struct_update_value() or
_testfunc_reg_struct_update_value():
0:00:44 load avg: 46.24 [137/407/1] test_ctypes failed -- running:
