In several places, we havegoto error; branches in bytecode instructions that occurafter modifying thenext_instr pointer. This is incorrect, since the error branch will behave as if the error occurred in thenew location (most often an adjacent instruction). The result could be as benign as an incorrect location in a traceback, or as problematic as incorrect control flow in or near atry/except block.

I tried for a bit to make the compiler emit code that did the wrong thing here, and I wasn't able to. So this is mostly a theoretical concern (but still worth fixing).

• PR:GH-99298: Don't perform jumps before error handling #99299

• PR:[3.11] GH-99298: Don't perform jumps before error handling #99343

• PR:GH-99298: Clean up attribute specializations #99398