_CHECK_FUNCTION interferes with partial evaluation

Feature or enhancement

Proposal:

A reminder of how _CHECK_FUNCTION looks like:

        tier2 op(_CHECK_FUNCTION, (func_version/2 -- )) {
            assert(PyStackRef_FunctionCheck(frame->f_funcobj));
            PyFunctionObject *func = (PyFunctionObject *)PyStackRef_AsPyObjectBorrow(frame->f_funcobj);
            DEOPT_IF(func->func_version != func_version);
        }

frame->f_funcobj becomes invalid once we start inlining functions. Thus we should "burn in" the function object version to be checked whenever possible, to not interfere with inlining and partial evaluation.

An added benefit is that the "burned in" version is also cheaper as it doesn't have to read from the frame struct, rather reading from the instruction itself in the JIT.

Has this already been discussed elsewhere?

No response given

Links to previous discussion of this feature:

No response

Linked PRs

• gh-126856

从 issue 中所示的 _CHECK_FUNCTION tier2 操作开始，检查函数被内联时如何使用 frame->f_funcobj。查看关联的 PR gh-126856，并确定是否可以将函数版本固化到指令中，而不干扰部分求值；完成的标准是，在可能的情况下，版本检查不再依赖已失效的 frame 引用。