Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

wasm-ctor-eval: Properly eval strings #6276

Merged
merged 1 commit into from
Feb 5, 2024

Conversation

kripken
Copy link
Member

@kripken kripken commented Feb 5, 2024

#6244 tried to do this but was not quite right. It treated a string like an array
or a struct, which means create a global for it. But just creating a global isn't
enough, as it needs to also be sorted in the right place etc. which requires
changes in other places. But there is a much simpler solution here: string
constants are just constants, which we can emit in-line, so do that.

@kripken kripken requested a review from tlively February 5, 2024 21:06
@kripken kripken enabled auto-merge (squash) February 5, 2024 21:14
@kripken kripken merged commit a549c59 into WebAssembly:main Feb 5, 2024
14 checks passed
@kripken kripken deleted the ctor-eval.string.simpler branch February 5, 2024 21:44
radekdoulik pushed a commit to dotnet/binaryen that referenced this pull request Jul 12, 2024
WebAssembly#6244 tried to do this but was not quite right. It treated a string like an array
or a struct, which means create a global for it. But just creating a global isn't
enough, as it needs to also be sorted in the right place etc. which requires
changes in other places. But there is a much simpler solution here: string
constants are just constants, which we can emit in-line, so do that.
@gkdn gkdn mentioned this pull request Aug 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants