feat(evm): add lazy JIT with OSR for multipass mode#442
Draft
starwarfan wants to merge 1 commit into
Draft
Conversation
⚡ Performance Regression Check Results✅ Performance Check Passed (interpreter)Performance Benchmark Results (threshold: 25%)
Summary: 194 benchmarks, 0 regressions ✅ Performance Check Passed (multipass)Performance Benchmark Results (threshold: 25%)
Summary: 194 benchmarks, 1 regressions |
Background JIT compilation runs in a separate thread while the
interpreter handles the first invocation. At JUMP/JUMPI, the interpreter
checks whether JIT code has become available and promotes execution
mid-flight via On-Stack Replacement (saving stack/memory to EVMInstance
and entering the JIT at the target PC through its indirect jump table).
Enabled by default; disable with DTVM_EVM_LAZY_JIT=false or
set_option("lazy","false").
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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
1 participant
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.
Background JIT compilation runs in a separate thread while the interpreter handles the first invocation. At JUMP/JUMPI, the interpreter checks whether JIT code has become available and promotes execution mid-flight via On-Stack Replacement (saving stack/memory to EVMInstance and entering the JIT at the target PC through its indirect jump table).
Enabled by default; disable with DTVM_EVM_LAZY_JIT=false or set_option("lazy","false").
1. Does this PR affect any open issues?(Y/N) and add issue references (e.g. "fix #123", "re #123".):
2. What is the scope of this PR (e.g. component or file name):
3. Provide a description of the PR(e.g. more details, effects, motivations or doc link):
4. Are there any breaking changes?(Y/N) and describe the breaking changes(e.g. more details, motivations or doc link):
5. Are there test cases for these changes?(Y/N) select and add more details, references or doc links:
6. Release note