-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Update wasmi
differential fuzzing
#4818
Comments
Updating would be great! If you'd like to send a PR I'd be happy to review. If you've got ideas about how to improve the differential fuzzing interface feel free to throw those in as well! |
Subscribe to Label Actioncc @fitzgen
This issue or pull request has been labeled: "fuzzing"
Thus the following users have been cc'd because of the following labels:
To subscribe or unsubscribe from this label, edit the |
Cool, I will come up with a PR in the next days. I have not yet taken an in-depth look at the Wasmtime fuzzing interface but will do when I am working on it and maybe come up with improvements. :) |
Wasmtime has implemented differential fuzzing against the
wasmi
interpreter. However, the currently supportedwasmi
version is very old and outdated.Benefits
The
wasmi
interpreter has since evolved quite a lot and could be helpful to more extensively fuzzy test against Wasmtime's feature set.wasmi
versions instead of ancient one.wasmi
only supported Wasm MVP.wasmi
versions are a lot faster.wasmi
versions offer an API similar to the API of Wasmtime, therefore fuzz testing code should become slightly cleaner.Downsides
The biggest downside is that the newer
wasmi
versions are not as battle tested as the old ones and therefore we might risk some false positives on thewasmi
side which could introduce noise.Implementation
I would open a PR myself if this issue is accepted. Shouldn't be too hard to update.
Alternatives
Stay on the current old
wasmi
version since it is quite stable and battle tested.The text was updated successfully, but these errors were encountered: