gh-132532: Add CHECK_PERIODIC instruction and use it for CALLs instead of the uop version.

[iritkatriel]

• Issue: Make it possible for the jit to deopt to tier1 upon interrupts #132532

[iritkatriel]

@gaogaotiantian this PR adds an instruction (CHECK_PERIODIC) after each call. So now pdb.set_trace() sees that as the next instruction, and thinks it's breaking one line earlier. How do you suggest we fix this? Skip the CHECK_PERIODIC instruction (where would the happen?)

[gaogaotiantian]

The test_pdb failure is not a real failure. We should just fix(remove) the test. It was a corner case where the instruction after CALL (POP_TOP) does not have a line number associated with it - and we should not stop there because missing line number would frustrate pdb. However, if the following instruction is CHECK_PERIODIC and it has a line number, we should just stop there.

[iritkatriel]

CHECK_PERIODIC has the same line number as the CALL of set_trace(). So it will look like we stopped just before the set_trace call. I don't think that's what we want.

[gaogaotiantian]

That is what we want. The existing test that failed is an exception, which stopped at the next line. We put a lot of effort to make breakpoint() stop at breakpoint(), so this is a desired behavior.

[iritkatriel]

I needed to make this change because otherwise the exception is not swallowed (seems that it shows up after the self.assertRaises call has returned).

[markshannon]

It looks like the specialize_method_descriptor needs to account for the CHECK_PERIODIC before the POP_TOP, and presumably CALL_LIST_APPEND will need to skip the two following instructions.