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 florin.papa
Recipients florin.papa, r.david.murray, skrah, vstinner, zach.ware
Date 2015-10-02.15:33:19
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> Why not enablind the option by default if GCC 5.1 or newer is detected? Is there a risk of breaking third-party extensions?
> Should we pass the MPX compiler options to third-party extensions by way?
On a processor that does not support MPX technology, MPX specific instructions will be replaced by nop's and will introduce a performance loss. Also, third party extensions might need to be patched in order to work with MPX. One example is the math module, which needed the bnd_legacy attribute to disable instrumentation when calling libc functions (which are not instrumented and generated compile errors).

> I'm not sure that it's ok to add such change to Python 2.7. It's border line between new feature and supporting a new architecture.
I believe that Python 2.7 should benefit from this change, since it is still used in real life applications, one example being Openstack Swift.
Date User Action Args
2015-10-02 15:33:20florin.papasetrecipients: + florin.papa, vstinner, r.david.murray, skrah, zach.ware
2015-10-02 15:33:20florin.papasetmessageid: <>
2015-10-02 15:33:20florin.papalinkissue25300 messages
2015-10-02 15:33:19florin.papacreate