[New-bugs-announce] [issue29502] Should PyObject_Call() call the profiler on C functions, use C_TRACE() macro?

[STINNER Victor]

New submission from STINNER Victor:

call_function() and do_call_core() functions of Python/ceval.c use C_TRACE() macro to call the profiler, but PyObject_Call() and similar functions like _PyObject_FastCallKeywords() don't.

Is it a bug or a deliberate choice for performance?

Since PyObject_Call() and similar functions have now fast paths, I don't think that it's still needed to have these fast paths in ceval.c too. But I kept fast paths in ceval.c because of C_TRACE().

----------
components: Interpreter Core
messages: 287343
nosy: haypo, inada.naoki, serhiy.storchaka
priority: normal
severity: normal
status: open
title: Should PyObject_Call() call the profiler on C functions, use C_TRACE() macro?
type: behavior
versions: Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29502>
_______________________________________