Repository navigation
gh-161827: Mark _PyEval_EvalFrameDefault as Py_NO_INLINE - #161829
Conversation
Signed-off-by: Iason Krommydas <iason.krom@gmail.com>
|
Thanks @ikrommyd for the PR, and @Fidget-Spinner for merging it 🌮🎉.. I'm working now to backport this PR to: 3.14, 3.15. |
|
GH-161833 is a backport of this pull request to the 3.15 branch. |
|
GH-161834 is a backport of this pull request to the 3.14 branch. |
…ythonGH-161829) pythongh-161827: Mark _PyEval_EvalFrameDefault as Py_NO_INLINE Signed-off-by: Iason Krommydas <iason.krom@gmail.com>
|
|
|
@freakboy3742: I'm not sure why the iOS/Android ARM64 buildbot is low on disk space. The simulator log directory from #140151 (comment) was only 3 GB, but I deleted it anyway. I also freed up 10 GB by deleting /Users/ec2-user/Library/Developer, because no development tools are being used by that account. That was enough to allow the buildbots to resume, but unless we remove something else it probably won't be long until they break again. I've found simulator-related files in several places:
This seems excessive, but I'm not sure what the cause is. When I run |
As discussed in #161827, with the tail-calling interpreter
_PyEval_EvalFrameDefaultcan get inlined into its callers (e.g. with Clang PGO) and no longer appear in the native call stack. This marks itPy_NO_INLINEso tools that rely on finding it keep working._PyEval_EvalFrameDefaultnot in the call stack when interpreter is built with--with-tail-call-interp#161827