Skip to content
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

core/vm: tweak the --vm.ewasm= option format #17895

Closed

Conversation

gballet
Copy link
Member

@gballet gballet commented Oct 11, 2018

wagon will also need to use the --vm.ewasm= option to see if contract metering should be enabled. Since this is also useful to #17050, might as well make it generic. The goal is to have options passed as `--vm.ewasm=option1:value1,option2:value2,..."

@gballet gballet requested a review from karalabe October 11, 2018 13:41
@gballet gballet requested a review from holiman as a code owner October 11, 2018 13:41
@gballet gballet mentioned this pull request Oct 22, 2018
@gballet
Copy link
Member Author

gballet commented Oct 22, 2018

@karalabe @holiman something cute to motivate you: 🐈

@karalabe
Copy link
Member

grumpy

@@ -43,7 +43,7 @@ type Config struct {
JumpTable [256]operation

// Type of the EWASM interpreter
EWASMInterpreter string
EWASMInterpreter map[string]string
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The interpreter config should remain a string. There's no point in expanding it in eth/backend. Just split it where you actually need it (in the EWASM's constructor inside core/vm).

@gballet
Copy link
Member Author

gballet commented Oct 24, 2018

Not gonna argue with a grumpy cat face, I'll close it right away ;)

@gballet gballet closed this Oct 24, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants