[wasm][R2R] more_tailcalls reads out of bounds

[lewing]

Description

JIT/Directed/tailcall/more_tailcalls traps during static non-generic tail recursion in browser-wasm CoreCLR ReadyToRun execution.

Reproduction Steps

Run the default runtime pipeline for #133463 at commit 452dea3aba16d97244508b8a0fef4643de8dd26e (Azure DevOps build 1589007, test run 43860850).

Expected behavior

The test completes with exit code 100.

Actual behavior

Static non-generic:
RuntimeError: memory access out of bounds
    at WasmR2RToInterpreterThunk(vp)
    at more_tailcalls_Program__Calc
    at more_tailcalls_Program__CalcStaticOther
    at more_tailcalls_Program__CalcStatic

Regression?

Unknown; exposed by the restored browser-wasm R2R lane.

Known Workarounds

Skip only this test for wasm ReadyToRun while retaining other tailcall and non-R2R coverage.

Configuration

• CoreCLR browser-wasm
• Checked runtime
• ReadyToRun / crossgen2
• Node.js 23.11.1

Other information

Umbrella tracking: #133305.

Note

This issue was authored with GitHub Copilot.

[dotnet-policy-service]

Tagging subscribers to 'arch-wasm': @lewing, @pavelsavara
See info in area-owners.md if you want to be subscribed.

[dotnet-policy-service]

Tagging subscribers to this area: @dotnet/crossgen-contrib
See info in area-owners.md if you want to be subscribed.

[MihuBot]

I'm a bot. Here is a possible related and/or duplicate issue (I may be wrong):

• Wasm: more_tailcalls fails with test assembly R2R #131890

[lewing]

Closing as a duplicate of #131890, which predates the restored lane and documents the same more_tailcalls wasm ReadyToRun limitation. The exclusion in #133463 now references the existing tracker.

Note

This comment was drafted with GitHub Copilot.