-
Notifications
You must be signed in to change notification settings - Fork 294
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
EVM instructions synthetic benchmarks #278
Conversation
77ce0e8
to
88e5085
Compare
5e34b29
to
440c0dc
Compare
Codecov Report
@@ Coverage Diff @@
## master #278 +/- ##
=======================================
Coverage 99.75% 99.75%
=======================================
Files 24 24
Lines 3655 3655
=======================================
Hits 3646 3646
Misses 9 9
Flags with carried forward coverage won't be shown. Click here to find out more. |
440c0dc
to
a24a30a
Compare
switch (kind) | ||
{ | ||
case InstructionKind::push: | ||
return stack_limit * (push(opcode, {}) + OP_POP); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What's the idea behind using stack_limit
as a limit in min_stack
mode? It could as well fill up the code size limit.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You can notice that both min_stack
and full_stack
have exactly the same instructions just with different order.
d648378
to
151fc83
Compare
bdc3fa3
to
0ababf7
Compare
09f8b59
to
49f30b7
Compare
1a3611f
to
21a5198
Compare
This introduces a set of on-demand generated EVM bytecodes available in the evmone-bench tool. Each bytecode tries to stress a single "low-level" EVM instruction. Instructions are grouped by their stack requirements and there are also two main modes of the structure of the generated bytecodes.
See: https://notes.ethereum.org/@chfast/benchmarking-evm-instructions