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 skrah
Recipients florin.papa, pitrou, r.david.murray, rhettinger, skrah, vstinner, zach.ware
Date 2015-10-27.13:56:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> The Python MPX binary will be built with –O0 because other optimization levels will change instruction order and cause crashes, making it useful for debugging purposes.

I've trouble understanding this: Is the gcc mpx feature not stable?

Looking at the patch, we'd introduce many new macros for everyone
to learn, but I'm generally not too enthusiastic about the proliferation
of memory protection schemes after having been bitten by a bug in
FORTIFY_SOURCE memmove wrappers. :(
Date User Action Args
2015-10-27 13:56:17skrahsetrecipients: + skrah, rhettinger, pitrou, vstinner, r.david.murray, zach.ware, florin.papa
2015-10-27 13:56:17skrahsetmessageid: <>
2015-10-27 13:56:17skrahlinkissue25300 messages
2015-10-27 13:56:16skrahcreate