-
Notifications
You must be signed in to change notification settings - Fork 15
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
chore: update to compatibility with latest version of vm2 #9
Conversation
Benchmark results:
|
Looks like vm2 will need to be public first. Also, I have realized I have to make more changes to the VM's interface to be able to integrate into core, so I think it makes sense to postpone this a bit. |
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.
@joonazan sure, take your time.
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.
Could you squash your commits and force-reapply them? Unfortunately the base was changed after merging v1.5.0, and I'd like not to resolve all these conflicts manually.
@hedgar2017 I just removed all your commits that were not related to vm2 and the conflicts went away. This is ok because they are in main anyway, right? |
Yes, I believe the history got broken is some way after merging |
a24ff19
to
54e8a96
Compare
685c2a5
to
d1fd458
Compare
Had to adjust the integration a bit because of vm2 interface changes. Adjusted the amount of gas passed to the VM.
With this version vm2 only fails TransientStorage tests. Those opcodes are unimplemented.