evm: opcode benchmarks #3531
Draft
evm: opcode benchmarks #3531
Conversation
This file contains 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.
Originally intended for #3529, but this can be used as standalone.
This PR creates a very simple "opcode benchmark". It reads all stack information from
stackDeltafrom EOF. Note: this stack delta only contains opcodes available in EOF, so opcodes asCALLare not in there.The benchmark simply setups the stack with the right amount of inputs (all zeros), then performs the operation, and then pops any outputs if the opcode has them. Then it jumps back (it loops forever). This is obviously a very naive test, for instance for the ADD opcode it will thus keep performing
0 + 0the entire time.