fitzgen opened PR #13660 from fitzgen:no-ir-globals-in-wasm-global-translation to bytecodealliance:main:
<!--
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 #13660.
fitzgen requested wasmtime-compiler-reviewers for a review on PR #13660.
fitzgen requested wasmtime-core-reviewers for a review on PR #13660.
:thumbs_up: alexcrichton submitted PR review.
:speech_balloon: alexcrichton created PR review comment:
Heh it's a little ironic seeing that "not move implies can move here"
:speech_balloon: alexcrichton created PR review comment:
Could this whole type be removed in favor of a maybe
.maybe_const_global(...)method that returns the aboveConstantoptionally?
fitzgen updated PR #13660.
fitzgen has enabled auto merge for PR #13660.
fitzgen added PR #13660 Do not use ir::GlobalValue when translating Wasm globals to the merge queue.
:check: fitzgen merged PR #13660.
fitzgen removed PR #13660 Do not use ir::GlobalValue when translating Wasm globals from the merge queue.
Last updated: Jul 29 2026 at 05:03 UTC