Skip to content
This repository has been archived by the owner on Aug 2, 2022. It is now read-only.

Add a new WASM backend: wabt #5416

Merged
merged 2 commits into from
Sep 14, 2018
Merged

Add a new WASM backend: wabt #5416

merged 2 commits into from
Sep 14, 2018

Conversation

spoonincode
Copy link
Contributor

Add a new WASM backend using wabt’s interpreter. This interpreter is considerably faster than the current default of binaryen — a replay on the mainnet typically completes in less than half the time compared to binaryen.

For now this will be considered experimental.

Add a new WASM backend using wabt’s interpreter. This interpreter is considerably faster than the current default of binaryen — a replay on the mainnet typically completes in less than half the time compared to binaryen.
Copy link
Contributor

@wanderingbort wanderingbort left a comment

Choose a reason for hiding this comment

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

I really only kicked the tires a bit by checking out memory translation and overflow stuff. The rest, I'm leaning on unit tests for.

@spoonincode spoonincode merged commit a73da77 into develop Sep 14, 2018
@spoonincode spoonincode deleted the wabt branch September 14, 2018 21:40
@abourget
Copy link
Contributor

When do you expect this to graduate from its experimental status?

@maoueh
Copy link
Contributor

maoueh commented Sep 20, 2018

Maybe this issue might shed some lights: #5754

@spoonincode
Copy link
Contributor Author

When do you expect this to graduate from its experimental status?

ah, yeah, that comment was written when the PR was fresh over 25 days ago. Since then it has been tested more. By all objective measures it is better than binaryen. No known problems with it either. You will have to use your own judgement for when it is safe to enable on your own network & nodes. But as pointed out it will be the default in 1.4.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants