You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+1-4Lines changed: 1 addition & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -56,7 +56,7 @@ Why not LLVM JIT-in-Wasm right now:
56
56
57
57
Why not full NIR->Wasm backend today:
58
58
- Mesa does not ship a complete NIR->Wasm backend for this use case.
59
-
-We built a simple proof-of-concept for a minimal pattern, but a full backend from scratch is a large compiler project and not realistic for a single maintainer effort.
59
+
-A full backend from scratch is a large compiler project and not realistic for a single maintainer effort.
60
60
61
61
Current strategy:
62
62
- Keep `clang_wasm_runtime_smoke` as a clang-in-wasm toolchain proof path.
@@ -154,13 +154,10 @@ It validates:
154
154
155
155
This gives a realistic loader flow for consumers that use Volk, while keeping dispatch pinned to the wasm ICD path.
156
156
157
-
`smoke_poc_nir_to_wasm` is kept as an experimental proof-of-concept path and is not the main production direction.
158
-
159
157
Current shader-path split:
160
158
-`lavapipe_runtime_smoke` injects runtime-generated SPIR-V (from Wasmer `clspv` by default) into the smoke module and validates Vulkan compute dispatch in the Mesa wasm driver.
161
159
-`clang_wasm_runtime_smoke` validates the clang-in-wasm toolchain path and runs an SPIR-V probe through a Wasmer runtime command (`clspv` package entrypoint by default).
162
160
- If that command is unavailable, smoke falls back to a direct `--target=spirv32` probe and reports the provider and failure reason.
163
-
-`smoke_poc_nir_to_wasm` is a separate experimental check and is not part of `runtime_smoke`.
0 commit comments