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

Gate wasm-smith component support behind a feature #1847

Merged

Conversation

alexcrichton
Copy link
Member

This feature is additionally off-by-default because the component support of wasm-smith has fallen quite far behind where components are at today.

This feature is additionally off-by-default because the component
support of `wasm-smith` has fallen quite far behind where components are
at today.
Copy link
Member

@fitzgen fitzgen left a comment

Choose a reason for hiding this comment

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

Maybe we should just remove this, since we are fuzzing components with a different approach in wasmtime? AFAIK, no one is using this?

@alexcrichton
Copy link
Member Author

Probably yeah, it's not too much of a burden to have though and might be a good starting point in the future. I think though we need to rearchitect things along the lines of the "top down" instruction generation idea from wasm-smith where we generate things "top down" rather than bottom-up (or both). I leave this as a problem for a future-someone though.

@alexcrichton alexcrichton added this pull request to the merge queue Oct 7, 2024
Merged via the queue into bytecodealliance:main with commit f34cfc8 Oct 7, 2024
30 checks passed
@alexcrichton alexcrichton deleted the gate-smith-component branch October 7, 2024 20:14
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