STINNER Victor added the comment: 2015-03-03 13:49 GMT+01:00 Serhiy Storchaka <rep...@bugs.python.org>: >> 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 :-) ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue23571> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
