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 vstinner
Recipients serhiy.storchaka, vstinner
Date 2015-03-03.13:16:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In-reply-to <2020551.UHYr1Dyx1P@raxxla>
2015-03-03 13:49 GMT+01:00 Serhiy Storchaka <>:
>> If the patch has a significant overhead: _Py_CheckFunctionResult() may be
>> marked to be inlined, and PyCFunction_Call() and PyObject_Call() checks may
>> be marked as unlikely using GCC __builtin_expect(), something like:
> Could you please open separate issue or even a topic on Python-Ideas for
> Py_likely/Py_unlikely? I prefer spelling _Py_LIKELY.

I'm not really interested by micro-benchmark here :-) I also propose
solutions *if* my patch makes the code slower.

Since __builtin_expect() may have a negative effect on performances, I
would prefer to avoid it if we can :-)
Date User Action Args
2015-03-03 13:16:08vstinnersetrecipients: + vstinner, serhiy.storchaka
2015-03-03 13:16:08vstinnerlinkissue23571 messages
2015-03-03 13:16:08vstinnercreate