Start tests with a blank slate of features instead of with the default set of features enables (ensures each test explicitly specifies required features)
Reuse test features from wasmtime_wast_util to avoid duplicating listings of features. Also shares logic for "should this compiler fail this test because of unsupported features".
Move logic in tests/wast.rs to apply test configuration to a Config to a new location that can be shared across suites.
Add a new feature for simd and flag tests that need it with the feature.
This is done in preparation for adding a new compiler strategy of Pulley to be able to flag tests as passing for pulley or not.
This issue or pull request has been labeled: "fuzzing"
Thus the following users have been cc'd because of the following labels:
* fitzgen: fuzzing
To subscribe or unsubscribe from this label, edit the .github/subscribe-to-label.json configuration file.
[Learn more.](https://github.com/bytecodealliance/subscribe-to-label-action)
Start tests with a blank slate of features instead of with the default set of features enables (ensures each test explicitly specifies required features)
Reuse test features from
wasmtime_wast_util
to avoid duplicating listings of features. Also shares logic for "should this compiler fail this test because of unsupported features".Move logic in
tests/wast.rs
to apply test configuration to aConfig
to a new location that can be shared across suites.Add a new feature for
simd
and flag tests that need it with the feature.This is done in preparation for adding a new compiler strategy of Pulley to be able to flag tests as passing for pulley or not.