alexcrichton opened PR #14685 from alexcrichton:cm-memory64-fixmes to bytecodealliance:main:
Wasmtime generally has no support for memory64 components at runtime, but my theoretical hope is that it'll be easier to implement this in the future if relevant locations are at least tagged with needing handling one way or another. This adds more comments throughout component-model-async bits to mirror what's already being done for the rest of the runtime.
<!--
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 review the Bytecode Alliance's AI tool usage policy at
https://github.com/bytecodealliance/governance/blob/main/AI_TOOL_POLICY.mdPlease ensure all communication follows the code of conduct:
https://github.com/bytecodealliance/wasmtime/blob/main/CODE_OF_CONDUCT.md
-->
alexcrichton requested cfallin for a review on PR #14685.
alexcrichton requested wasmtime-compiler-reviewers for a review on PR #14685.
alexcrichton requested wasmtime-core-reviewers for a review on PR #14685.
:thumbs_up: cfallin submitted PR review.
cfallin added PR #14685 Sprinkle some FIXMEs for memory64 support to the merge queue.
:check: cfallin merged PR #14685.
cfallin removed PR #14685 Sprinkle some FIXMEs for memory64 support from the merge queue.
Last updated: Oct 31 2026 at 23:03 UTC