Target Python 3.11 in byte code interpreter #252
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We also compile the examples with Python 3.11. As the changes to the interpreter so far are simply name changes we disable the CPython interpreter tests.
We update framework and implementation classes that we need for execution of 3.11 byte code. The main affected classes are PyCode, PyFrame and PyFunction, and their implementations for CPython byte code. PyFunction is added because in 3.11 all frames have a function object, even a top level module. Other changes are just supporting methods and tweaks. Opcodes are not implemented yet, so we can't run code, but we can load it.
We re-enable a batch of tests in CPython311CodeTest and implement the opcodes they need in eval(). A number of object and utility classes have to up their game in support.
|
At this point, the set of tests that ran before the change of target to 3.11, now runs again. I'll leave this to simmer for a few weeks before merging. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We've been targeting 3.8 and that looks a bit old now. Work on the PEG parser will be easier with 3.11. Some CPython internals are better thought out, providing a clearer pattern to copy. On the down-side, parts of the CPython interpreter are significantly more complicated, but these are internal optimisations we need not emulate.
In particular, we will not attempt to emulate CPython's byte code "quickening" since we intend to generate JVM code most of the time and interpret CPython byte code only where there's no alternative. However, it is also a good place to develop from.
In the first step we simply rename classes without changing them and also compile the examples with Python 3.11. As the changes to the interpreter so far are simply name changes we disable the CPython interpreter tests. Something more interesting will follow.