Skip to content

Conversation

@kripken
Copy link
Member

@kripken kripken commented Jan 25, 2024

99% sure this started erroring on the fuzzer due to the testcase from #6234

@kripken kripken requested a review from tlively January 25, 2024 19:25
@kripken kripken merged commit 482f3aa into WebAssembly:main Jan 25, 2024
@kripken kripken deleted the eval.string branch January 25, 2024 20:49
kripken added a commit that referenced this pull request 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.
radekdoulik pushed a commit to dotnet/binaryen that referenced this pull request Jul 12, 2024
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