-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
[WASI] bump WASI SDK 24 #105317
[WASI] bump WASI SDK 24 #105317
Conversation
Tagging subscribers to 'arch-wasm': @lewing |
cc @dicej |
38cf8e4
to
7d2c129
Compare
Co-authored-by: Joel Dice <joel.dice@fermyon.com>
Co-authored-by: Joel Dice <joel.dice@fermyon.com>
Co-authored-by: Joel Dice <joel.dice@fermyon.com>
Co-authored-by: Joel Dice <joel.dice@fermyon.com>
@@ -368,8 +347,8 @@ JS_ENGINES = [NODE_JS] | |||
Condition="'$(ActualWasiSdkVersion)' != '$(ExpectedWasiSdkVersion)'" /> | |||
|
|||
<!-- LLVM in WASI SDK 22 will call wasm-opt when found on the PATH. But it will fail because wasm-opt can't read the WASM components. | |||
After we upgrade to WASI SDK 23, we could use no-wasm-opt LLVM option to avoid this issue. | |||
See https://github.com/llvm/llvm-project/pull/95208#issuecomment-2220400454 | |||
After we upgrade to WASI SDK 23.x, we could use no-wasm-opt LLVM option to avoid this issue. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this comment still relevant?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe that it will land with LLVM 19, we are still on LLVM 18.
I will update the comment in another PR and I updated #104773
VERSION22PATCHED
toVERSION24
23.0.1
v0.2.1
0.29
Contributes to #104773
Contributes to #105290