alexcrichton opened PR #9567 from alexcrichton:improve-fuzz-memory-config
to bytecodealliance:main
:
This commit updates how the
NormalMemoryConfig
works during fuzzing. Previously this was either 0 or an arbitrary 32-bit number. This ended up not not handling cases such as 4GiB exactly which is 1 larger than the 32-bit range. Additionally 33+-bit numbers were never tested. This intends to expand our fuzz coverage here by most of the time using the default settings ofConfig
and then otherwise selecting amongst an "interesting" set of numbers such as 0, powers of two, etc.<!--
Please make sure you include the following information:
If this work has been discussed elsewhere, please include a link to that
conversation. If it was discussed in an issue, just mention "issue #...".Explain why this change is needed. If the details are in an issue already,
this can be brief.Our development process is documented in the Wasmtime book:
https://docs.wasmtime.dev/contributing-development-process.htmlPlease ensure all communication follows the code of conduct:
https://github.com/bytecodealliance/wasmtime/blob/main/CODE_OF_CONDUCT.md
-->
alexcrichton requested fitzgen for a review on PR #9567.
alexcrichton requested wasmtime-fuzz-reviewers for a review on PR #9567.
fitzgen submitted PR review.
fitzgen merged PR #9567.
Last updated: Dec 23 2024 at 13:07 UTC