{{ message }}
⚡ Bolt: Remove redundant frame lookups in VM executor - #59
Merged
Conversation
Co-authored-by: Tcode-Motion <188012755+Tcode-Motion@users.noreply.github.com>
Contributor
Tcode-Motion
marked this pull request as ready for review
September 4, 2026 05:39
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.
💡 What: Removed redundant
self.frames.last_mut()lookups inruntime/vm/src/executor.rsinside control flow opcodes (Jump,JumpIfTrue,JumpIfFalse,Try,EndTry).🎯 Why: In the hot interpreter loop, fetching the current frame inside these opcodes was doing unnecessary bounds checks and method calls when a valid mutable
framereference was already acquired at the start of the loop iteration. This reduces overhead in the fetch-decode-execute loop.📊 Impact: Faster evaluation of tight loops and control flow structures due to reduced pointer chasing and bounds checking overhead on the hottest execution paths.
🔬 Measurement: Verify by running
cargo test -p techscript_vmor using the internal VM profiler on standard examples.PR created automatically by Jules for task 17600582422919581721 started by @Tcode-Motion