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 gregory.p.smith
Recipients Arfrever, benjamin.peterson, doko, eric.araujo, georg.brandl, gregory.p.smith, larry, python-dev, ronaldoussoren
Date 2013-02-19.22:05:17
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1361311517.51.0.183195200063.issue17192@psf.upfronthosting.co.za>
In-reply-to
Content
An update to libffi is needed for all maintained versions of Python.

In 2.7, we're running into the stack being misaligned in 32-bit x86 code which is something a libffi update fixes.  It is a simple patch:

 http://patchwork.ozlabs.org/patch/58128/

which comes to the official libffi releases via https://github.com/atgreen/libffi/commit/3f5b1375ab1e2b8e3d593e21b27097a4a50f9b83#src/x86/sysv.S.

The problem: without the stack being 16-byte aligned, code generated by modern compilers like recent gcc/g++ or clang assumed that the stack is 16 byte aligned and uses SSE instructions in some circumstances that require this.  Without this fix, any ctypes call into such code will crash.

Sure, that tiny patch could be cherry picked into our libffi, but we IMNSHO may as well just update the entire thing given that we embed a very old copy rather than use it as an external dependency.
History
Date User Action Args
2013-02-19 22:05:17gregory.p.smithsetrecipients: + gregory.p.smith, georg.brandl, doko, ronaldoussoren, larry, benjamin.peterson, eric.araujo, Arfrever, python-dev
2013-02-19 22:05:17gregory.p.smithsetmessageid: <1361311517.51.0.183195200063.issue17192@psf.upfronthosting.co.za>
2013-02-19 22:05:17gregory.p.smithlinkissue17192 messages
2013-02-19 22:05:17gregory.p.smithcreate