[User Story] RyuJIT for WebAssembly (Wasm)

[JulieLeeMSFT]

We are bringing RyuJIT support to WebAssembly in .NET 11 as an early preview, focused on delivering a functional, though not yet fully optimized, experience for Blazor and .NET applications targeting Wasm.

.NET 11, the early preview, will enable basic scenarios and validate the new backend, allowing the team to gather feedback and address gaps ahead of broader migration from Mono runtime. Performance improvements, expanded feature coverage, and full consolidation are planned for subsequent releases, with .NET 12 and beyond targeting production readiness and optimized developer experience.

RyuJIT Base Line

• [Wasm RyuJIT] Object Writer #121143
• [Wasm RyuJIT] Basic Control Flow #121178
• [Wasm RyuJIT] Basic WASM codegen #121208
• [Wasm RyuJIT] Stub Generator Design/Development #121595
• [Wasm RyuJIT] Calling Convention #121215
• [Wasm RyuJIT] R2R #121257
• [Wasm RyuJIT] Interpreter Integration #121600

Exception Handling & GC Support

• [Wasm RyuJIT] EH & GC Design #121651
• [Wasm RyuJIT] Stack Tracing #121830
• [Wasm RyuJIT] Conservative GC #121831
• [Wasm RyuJIT] Shadow Stack Walker for Exception Handling #121832

SIMD, Interop, and Basic Optimizations

• [Wasm RyuJIT] Interop/Pinvoke Design #124103
• Interop/Pinvoke
• SIMD & Intrinsics
• Runtime Async [Wasm Ryujit]: implement runtime-async codegen for R2R Wasm #131167
• Profiling (Identify key methods)
• Diagnostics (event pipe)
• [Wasm RyuJIT] Precise GC #121854
• Performance for a few scenarios (Size & Speed)

Out of Scope (Needs to revisit later)

• Multi-threading for browser
• WASI
• WASM64

[dotnet-policy-service]

Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch
See info in area-owners.md if you want to be subscribed.

[JulieLeeMSFT]

cc @kg, @AndyAyersMS, @adamperlin, @lewing, @janvorli, @steveisok, @SingleAccretion, @yowl.

[SingleAccretion]

Object Writer

FWIW, we have a WASM object writer downstream: https://github.com/dotnet/runtimelab/blob/feature/NativeAOT-LLVM/src/coreclr/tools/aot/ILCompiler.LLVM/CodeGen/WasmObjectWriter.cs. I presume for R2R purposes it will need to be a extended a bit to support "binary" (as opposed to relocatable) file generation.

[JulieLeeMSFT]

Object Writer

FWIW, we have a WASM object writer downstream: https://github.com/dotnet/runtimelab/blob/feature/NativeAOT-LLVM/src/coreclr/tools/aot/ILCompiler.LLVM/CodeGen/WasmObjectWriter.cs. I presume for R2R purposes it will need to be a extended a bit to support "binary" (as opposed to relocatable) file generation.

Thanks a lot, @SingleAccretion, for the pointer. @adamperlin needed it.

[yowl]

Should we add threads (for WASI) here, it's not available yet, but I hope it will be in the component model for example in the timeframes of .net 11 and 12

[JulieLeeMSFT]

Should we add threads (for WASI) here, it's not available yet, but I hope it will be in the component model for example in the timeframes of .net 11 and 12

Thanks. Added it to the potential future work. We have thought about it, but we need to go through another planning when we start .NET 12.

[JulieLeeMSFT]

Related Interpreter work to support wasm: #112748.