fitzgen opened PR #11169 from fitzgen:move-object-size-out-of-reserved-bits to bytecodealliance:main:
We are going to use those bits for other things as we implement https://github.com/bytecodealliance/wasmtime/issues/11162.
This also lets us increase the largest supported GC allocation to a full
u32::MAXbytes.<!--
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
-->
fitzgen requested alexcrichton for a review on PR #11169.
fitzgen requested wasmtime-compiler-reviewers for a review on PR #11169.
fitzgen requested wasmtime-core-reviewers for a review on PR #11169.
alexcrichton submitted PR review.
alexcrichton created PR review comment:
Is it worth adapting this test to the new limit of 32-bits?
fitzgen created PR review comment:
tests/misc_testsuite/gc/array-alloc-too-large.wastalready tests the 32-bit limit, so I think we are good.
fitzgen submitted PR review.
fitzgen updated PR #11169.
fitzgen has enabled auto merge for PR #11169.
fitzgen merged PR #11169.
Last updated: Dec 06 2025 at 06:05 UTC