diff options
| author | Ryuji Tsutsui <ryu22e+github@gmail.com> | 2023-11-15 15:40:19 (GMT) |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-11-15 15:40:19 (GMT) |
| commit | 0cfdd6e3d17fee8c1c1f4b42b2146abcb43aa34b (patch) | |
| tree | 6355e75687097080780a107bba8b89c30e82dacd | |
| parent | 422c0f030170490c001575303d9e628a0298d457 (diff) | |
| download | cpython-0cfdd6e3d17fee8c1c1f4b42b2146abcb43aa34b.zip cpython-0cfdd6e3d17fee8c1c1f4b42b2146abcb43aa34b.tar.gz cpython-0cfdd6e3d17fee8c1c1f4b42b2146abcb43aa34b.tar.bz2 | |
Fix typo in perf profiling docs (#112112)
| -rw-r--r-- | Doc/howto/perf_profiling.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Doc/howto/perf_profiling.rst b/Doc/howto/perf_profiling.rst index af7b67d..bb1c00e 100644 --- a/Doc/howto/perf_profiling.rst +++ b/Doc/howto/perf_profiling.rst @@ -97,7 +97,7 @@ Then we can use ``perf report`` to analyze the data: | | | | | |--2.97%--_PyObject_Malloc ... -As you can see, the Python functions are not shown in the output, only ``_Py_Eval_EvalFrameDefault`` +As you can see, the Python functions are not shown in the output, only ``_PyEval_EvalFrameDefault`` (the function that evaluates the Python bytecode) shows up. Unfortunately that's not very useful because all Python functions use the same C function to evaluate bytecode so we cannot know which Python function corresponds to which bytecode-evaluating function. |