6 Commits

Author	SHA1	Message	Date
Brandt Bucher	c7f5708714	GH-98686: Get rid of "adaptive" and "quick" instructions (GH-99182)	2022-11-09 10:50:09 -08:00
Guido van Rossum	f1a654648b	GH-98831: Simple input-output stack effects for bytecodes.c (#99120)	2022-11-08 08:22:56 -08:00
Guido van Rossum	7dcd28eb41	GH-98831: Implement super-instruction generation (#99084) ... Co-authored-by: C.A.M. Gerlach <CAM.Gerlach@Gerlach.CAM>	2022-11-06 09:40:47 -08:00
Guido van Rossum	d04899abb0	GH-99104: Update headers for bytecodes.c and generate_cases.py (#99112) ... Also tweak the labels near the end of bytecodes.c.	2022-11-04 17:40:43 -07:00
Guido van Rossum	c885623e9f	GH-98831: Auto-generate PREDICTED() macro calls (#99102) ... Co-authored-by: Brandt Bucher <brandtbucher@gmail.com>	2022-11-04 15:30:17 -07:00
Guido van Rossum	41bc101dd6	GH-98831: "Generate" the interpreter (#98830) ... The switch cases (really TARGET(opcode) macros) have been moved from ceval.c to generated_cases.c.h. That file is generated from instruction definitions in bytecodes.c (which impersonates a C file so the C code it contains can be edited without custom support in e.g. VS Code). The code generator lives in Tools/cases_generator (it has a README.md explaining how it works). The DSL used to describe the instructions is a work in progress, described in https://github.com/faster-cpython/ideas/blob/main/3.12/interpreter_definition.md. This is surely a work-in-progress. An easy next step could be auto-generating super-instructions. **IMPORTANT: Merge Conflicts** If you get a merge conflict for instruction implementations in ceval.c, your best bet is to port your changes to bytecodes.c. That file looks almost the same as the original cases, except instead of `TARGET(NAME)` it uses `inst(NAME)`, and the trailing `DISPATCH()` call is omitted (the code generator adds it automatically).	2022-11-02 21:31:26 -07:00