feat(inspector): configure stepped opcodes - #149
Draft
DaniPopes wants to merge 21 commits into
Draft
Conversation
…code-config # Conflicts: # crates/evm2/src/evm/inspector.rs
…-config # Conflicts: # AGENTS.md # crates/evm2/src/evm/config.rs # crates/evm2/src/evm/inspector.rs # crates/evm2/src/evm/mod.rs # crates/evm2/src/interpreter/runtime.rs
Merging this PR will improve performance by 10.51%
|
| Benchmark | BASE |
HEAD |
Efficiency | |
|---|---|---|---|---|
| ⚡ | fibonacci-calldata |
258.4 µs | 233.8 µs | +10.51% |
Tip
Curious why this is faster? Comment @codspeedbot explain why this is faster on this PR, or directly use the CodSpeed MCP with your agent.
Comparing dani/inspector-opcode-config (9c0b153) with main (22b1fc1)
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.
Stacked on #151.
This adds an inspector configuration hook for declaring which opcodes need step hooks, then registers that config into the runtime execution table before inspected execution. Sparse configs execute uninterested opcodes through the normal dispatch path, while full opcode configs keep the normal table and run step hooks from the table dispatch loop instead of through every opcode wrapper.