perf: optimize jump table initialization and reuse - #6943
Open
ouy95917 wants to merge 1 commit into
Open
Conversation
yanghang8612
marked this pull request as ready for review
September 2, 2026 08:44
| if (VMConfig.allowTvmSelfdestructRestriction()) { | ||
| adjustSelfdestruct(table); | ||
| } | ||
| public static JumpTable prepareAndGetTable(boolean isConstantCall) { |
Collaborator
There was a problem hiding this comment.
Nice change — just to confirm, are these config-based adjustments expected to stay stable once this table has been prepared?
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
3 participants
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 does this PR do?
LATEST_VERSIONandnewLatestOperationSet().Why is this needed?
The previous implementation initialized jump tables for multiple historical versions even though only the latest version was selected for execution.
Transactions and constant calls also shared the same table, which allowed adjustments made for constant calls to affect transaction execution. In addition, configuration-dependent adjustments could be applied repeatedly during nested calls and contract creation.
This change centralizes the selection of the latest operation set and separates transaction and constant-call tables. It reduces startup initialization and repeated adjustment overhead while keeping the two execution paths isolated.
Tests