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 methane
Recipients methane, python-dev, rhettinger, serhiy.storchaka, vstinner, yselivanov
Date 2017-02-10.09:38:14
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1486719495.13.0.33028115516.issue29507@psf.upfronthosting.co.za>
In-reply-to
Content
Yes, I used --enable-optimization this time.
But my patch is not good for branch prediction of my CPU in this time.
I'm willing Object/call.c solves such placement issue.

BTW, since benefit of GetMethod is small, how about this?

* Add _PyMethod_FastCallKeywords
* Call it from _PyObject_FastCall*

_PyObject_FastCall* can use FASTCALL C function and method (PyCFunction),
and Python function (PyFunction).
Python method (PyMethod) is last common callable PyObject_FastCall* can't use FASTCALL.
History
Date User Action Args
2017-02-10 09:38:15methanesetrecipients: + methane, rhettinger, vstinner, python-dev, serhiy.storchaka, yselivanov
2017-02-10 09:38:15methanesetmessageid: <1486719495.13.0.33028115516.issue29507@psf.upfronthosting.co.za>
2017-02-10 09:38:15methanelinkissue29507 messages
2017-02-10 09:38:14methanecreate