bpo-45753: Interpreter internal tweaks

[markshannon]

The overall purpose of this PR is to help future work on inter-bytecode optimization and efficient support for tracing events.

This is a bit of an ugly PR as it attempts to do a few things which are conceptually only loosely related, but are interwoven in the code.

1. Specify a set of interpreter "registers", that is the parts of the interpreter state that are worth caching in local variables. This is nothing new, just a bit more explicit. These variables are currently:
   • frame. Pointer to the current InterpreterFrame
   • names and consts. Pointers to the names and consts tuples of the current code object. These could be merged into one in future (Merge co_names and co_consts into a single array. faster-cpython/ideas#92)
   • first_instr and next_instr. Pointers to the first and next instructions.
   • stack_pointer. The evaluation stack pointer.
2. Make all tracing events explicit as macros, and move them into instructions where appropriate.
3. Inline frame exit, entry and resumption where necessary to support above goals.

No meaningful change in performance

See faster-cpython/ideas#112 for motivation

https://bugs.python.org/issue45753

[markshannon]

Skipping NEWS as this is just a refactor. There is no change to behavior, API, or performance.

[markshannon]

The Windows failure appears to be a glitch.

[markshannon]

@pablogsal Could you take a look at the rearrangement of the code in RETURN_VALUE and YIELD_ instructions.
Does it seem reasonable to you?

[pablogsal]

@pablogsal Could you take a look at the rearrangement of the code in RETURN_VALUE and YIELD_ instructions.
Does it seem reasonable to you?

I'm currently unavailable until this Friday. Can you wait until then?

[markshannon]

@pablogsal Could you take a look at the rearrangement of the code in RETURN_VALUE and YIELD_ instructions.
Does it seem reasonable to you?

I'm currently unavailable until this Friday. Can you wait until then?

No problem

[brandtbucher]

Some comments while you wait for Pablo. Many are probably just for improving my own understanding of the changes here:

[bedevere-bot]

When you're done making the requested changes, leave the comment: I have made the requested changes; please review again.

[bedevere-bot]

🤖 New build scheduled with the buildbot fleet by @markshannon for commit 88610c7 🤖

If you want to schedule another build, you need to add the ":hammer: test-with-buildbots" label again.

[gvanrossum]

I have a few questions and nits but I think I understand this well enough to approve once you've replied to those -- you can take them or leave them.