Remove irregular stack effects

[markshannon]

As we move towards generating more components from the instruction definition file (bytecodes.c), it helps if the instructions have regular formats and stack effects.
Currently the stack effects can be simple, variable, conditional or complex.

• Simple: Does not depend on the operand (oparg)
• Variable: Either pops or pushes oparg * k items.
• Conditional: Pushes a value conditional on oparg & 1
• Complex: The stack effect depends on a set of flags embedded in oparg.

We can easily get rid of the complex case. There are only two cases, MAKE_FUNCTION and FORMAT_VALUE. Both can easily broken down into simple (and faster) parts.

We might want to get rid of condition stack effects, as it would simplify things, but performance may suffer as both LOAD_GLOBAL and LOAD_ATTR are conditional and they are performance critical.

Linked PRs

• GH-105678: Split MAKE_FUNCTION into MAKE_FUNCTION and SET_FUNCTION_ATTRIBUTE #105680
• gh-105678: document SET_FUNCTION_ATTRIBUTE #105843

[gvanrossum]

@markshannon Can this be closed yet? I doubt that we'll be removing conditional stack effects (at least conditional pushes). Note that we now support conditional pushes in the final op of a macro. (If needed the same approach could be used to support conditional pops in the first op.)

[markshannon]

Yes, this can be closed.
We might want to remove conditional stack effects in the future, but not now.