From 606d546df69fde8d5100db38dc86cf84b0492df7 Mon Sep 17 00:00:00 2001 From: Rich Geldreich Date: Fri, 13 Feb 2026 19:56:12 -0500 Subject: [PATCH] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index d61f818..645dbe2 100644 --- a/README.md +++ b/README.md @@ -161,7 +161,7 @@ chmod +x runwt.sh ./runwt.sh tough.ktx2 ``` -Unfortunately, 32-bit WASM WASI executables have tradeoffs vs. native executables: Limited memory (serious issue), and slower performance (somewhat mitigatable using WASM threading, which we support). 32-bit WASM WASI memory constraints limit the maximum image/texture size that can be compressed to XUASTC LDR to around 4 megapixels. For web, we can support both WASM and WASM64, which relaxes the memory constraints. As far as we know as of 2/2026, the WASI SDK still [doesn't officially support the wasm64-wasi target](https://github.com/WebAssembly/wasi-sdk/issues/212), but once it does we'll support it. +Unfortunately, 32-bit WASM WASI executables have tradeoffs vs. native executables: Limited memory (serious issue), and slower performance (somewhat mitigatable using WASM threading, which we support). 32-bit WASM WASI memory constraints limit the maximum image/texture size that can be compressed to XUASTC LDR to around 4 megapixels. For web, we can support both WASM and WASM64, which greatly improves the memory situation. As far as we know as of 2/2026, the WASI SDK still [doesn't officially support the wasm64-wasi target](https://github.com/WebAssembly/wasi-sdk/issues/212), but once it does we'll support it. ----