Skip to content

Enable bulk-memory by default in wasm-smith#1861

Merged
fitzgen merged 1 commit intobytecodealliance:mainfrom
alexcrichton:wasm-smith-config
Oct 10, 2024
Merged

Enable bulk-memory by default in wasm-smith#1861
fitzgen merged 1 commit intobytecodealliance:mainfrom
alexcrichton:wasm-smith-config

Conversation

@alexcrichton
Copy link
Copy Markdown
Member

The implementation of Arbitrary for Config already enabled it by default, so reflect this in the Default implementation as well.

The implementation of `Arbitrary for Config` already enabled it by
default, so reflect this in the `Default` implementation as well.
@fitzgen fitzgen added this pull request to the merge queue Oct 10, 2024
Merged via the queue into bytecodealliance:main with commit a300e5c Oct 10, 2024
@alexcrichton alexcrichton deleted the wasm-smith-config branch October 11, 2024 01:28
pchickey added a commit to bytecodealliance/wasmtime that referenced this pull request Nov 13, 2024
github-merge-queue bot pushed a commit to bytecodealliance/wasmtime that referenced this pull request Nov 13, 2024
* component-macro: paths are now an accessor on PackageSourceMap

* wast: WastArg enum is now non-exhaustive

and the error messages were mostly written the wrong way around

* upgrade to wasm-tools 220 release

* supply chain: vet of unicode-width and automatic changes

* github actions: upgrade to cargo-vet 0.10.0

* wasmtime requires ahash feature on hashbrown, a transitive must have been ticking it prior

* upgrade to wit-bindgen 0.35

which uses wasm-tools 220, eliminating the duplicate deps in the lockfile.

* vet wit-bindgen upgrade

* fuzzing: add WasmFeatures::EXTENDED_CONF to expected features

wasm-smith added it in bytecodealliance/wasm-tools#1861
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