This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author erik.bray
Recipients erik.bray, vinay.sajip, xiang.zhang
Date 2017-05-15.08:20:07
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1494836407.75.0.0301319163745.issue30353@psf.upfronthosting.co.za>
In-reply-to
Content
Thanks for pointing that out.  Indeed it's the same symptom, but slightly different cause.  libffi has different implementations of its calling routines for different architectures/platforms depending on the machine architecture and calling conventions used.  So this case is probably buggy for the arm64 implementation as well, as in #29804.

Off the top of my head I don't know a reliable way to check for this case, but this fix would work around the arm64 issue as well if I could check for that architecture easily at compile time.
History
Date User Action Args
2017-05-15 08:20:07erik.braysetrecipients: + erik.bray, vinay.sajip, xiang.zhang
2017-05-15 08:20:07erik.braysetmessageid: <1494836407.75.0.0301319163745.issue30353@psf.upfronthosting.co.za>
2017-05-15 08:20:07erik.braylinkissue30353 messages
2017-05-15 08:20:07erik.braycreate