perf(evm): reuse CFG memory proofs for CALL ranges - #585
Merged
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: 193 benchmarks, 0 regressions |
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
2 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.
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):
EVM multipass JIT CALL-family lowering, runtime CALL helpers, and EVM frontend/differential tests.
3. Provide a description of the PR(e.g. more details, effects, motivations or doc link):
Reuse CFG-propagated guaranteed memory-size facts for CALL, CALLCODE, DELEGATECALL, and STATICCALL when both the argument and return ranges are already covered.
The first commit adds prepared-memory runtime helpers while preserving the existing account-access, delegated-code, static-mode, call-gas, depth, and host-call ordering. The second commit selects those helpers only when both ranges are proven at the exact opcode PC; uncovered or dynamic ranges retain the generic expansion path, and zero-length ranges retain EVM empty-range semantics.
A 65-contract real-bytecode corpus selected the prepared path 125 times across 23 contracts. A sequential merge simulation with the COPY, KECCAK, and RETURN/REVERT CFG-proof consumers merged without conflicts.
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:
Validation:
./tools/format.sh formatand./tools/format.sh checkevmJitFrontendTests: 110/110 passed on this branchevmDifferentialTests: 27/27 passed, including identity-precompile output/gas equality and zero-length high-offset semantics6. Release note