JIT dispatch code instead of trie-tables computing index #56
Conversation
This file contains hidden or 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
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.
Currently, the VM/JIT uses trie-tables that generate data used by C code to look up indices for computing branch taken during multimethod dispatch. This PR introduces assembly code created JIT to compute the same thing without needing tables. The dependency tracking and management code stays effectively the same but instead manages vectors of code instead of trie tables. I introduced a BranchEntries API where I can then backend with Trie Tables or Dispatch funcs. The Trie Table is still used when JIT experimental feature is not specified.