Feature or enhancement

Proposal:

It seems _RECORD_BOUND_METHOD exists in bytecodes.c but is not implemented in optimizer_bytecodes.c This means _INIT_CALL_BOUND_METHOD fails to get probable method and does not continue optimizing the trace.

The problem with not doing this is that the _PUSH_FRAME at the call site for the bound method decides to hit bottom because it sees no code object :(. So any trace with a call to a bound method does not get optimized after the call. This is pretty bad...

Has this already been discussed elsewhere?

No response given

Links to previous discussion of this feature:

No response

Linked PRs

• gh-148438: implement _RECORD_BOUND_METHOD in JIT #148457