Repository navigation
builder: fix pointer size in wasm - #26281
Merged
Merged
Conversation
spytheman
approved these changes
Jan 8, 2026
spytheman
left a comment
spytheman
left a comment
Contributor
There was a problem hiding this comment.
Thank you @Krchi 🙇🏻 .
It is a reasonable solution for now, given that almost all existing wasm infrastructure expects wasm32, although it may be a problem for the future when wasm64 support becomes more widespread 🤔 . Anyway, that is a future problem.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
current wasm out file is wasm32, set pointer size before checker, and remove set in wasmgen