perf(evm): add soft-fallback opcode table for const memory precheck#484
Open
ys8888john wants to merge 2 commits into
Open
perf(evm): add soft-fallback opcode table for const memory precheck#484ys8888john wants to merge 2 commits into
ys8888john wants to merge 2 commits into
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 |
10d3724 to
36c6c38
Compare
36c6c38 to
2f99a8f
Compare
Contributor
There was a problem hiding this comment.
Pull request overview
This PR extends the EVM bytecode visitor’s const direct-memory precheck analysis by adding a 256-entry “opaque” opcode stack-effect table, allowing more non-memory-mutating opcodes to be simulated (instead of immediately rejecting the precheck plan). It also changes MSIZE handling to conservatively bail out to avoid semantic mismatches when memory-expansion is pre-applied.
Changes:
- Add
PrecheckOpaqueStackEffect+buildPrecheckOpaqueStackEffectTable()to model stack deltas for additional opcodes in the const-precheck simulator’s fallback path. - Update const-precheck simulation
default:handling to use the new table rather than unconditionally bailing. - Change
OP_MSIZEhandling in const-precheck simulation to hard-bail to avoid incorrect observed memory size.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Comment on lines
+1740
to
+1746
| static constexpr auto OpaqueEffects = | ||
| buildPrecheckOpaqueStackEffectTable(); | ||
| const PrecheckOpaqueStackEffect &Eff = | ||
| OpaqueEffects[static_cast<uint8_t>(Opcode)]; | ||
| if (Eff.Pops == kPrecheckBailSentinel) { | ||
| return {}; | ||
| } |
Comment on lines
1729
to
+1734
| case OP_MSIZE: | ||
| SimStack.push_back(makeUnknownConstU64()); | ||
| break; | ||
| default: | ||
| // MSIZE observes the precise memory size at the moment it executes. | ||
| // Hoisting expandMemoryIR to the BB entry would expand memory ahead | ||
| // of MSIZE and pollute its observed value, breaking EVM semantics | ||
| // (state root mismatch in vmIOandFlowOperations.msize). Hard-bail. | ||
| return {}; |
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.
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