[Wasm RyuJIT] Wasm control flow basics by AndyAyersMS · Pull Request #121417 · dotnet/runtime

AndyAyersMS · 2025-11-06T19:39:33Z

Determine how to emit Wasm control flow from the JIT's control flow graph.

Relies on loop-aware RPO to determine the block order. Currently only handles the main method. Assumes irreducible loops have been fixed upstream (which is not yet guaranteed; bails out if not so).

Doesn't actually do any emission, just prints a textual description in the JIT dump (along with a dot markup version).

Uses only LOOP and BLOCK. Tries to limit the extent of BLOCK.

Run for now as an optional phase even if not targeting Wasm, to do some stress testing.

Contributes to #121178

Determine how to emit Wasm control flow from the JIT's control flow graph. Relies on loop-aware RPO to determine the block order. Currently only handles the main method. Assumes irreducible loops have been fixed upstream (which is not yet guaranteed; bails out if not so). Doesn't actually do any emission, just prints a textual description in the JIT dump (along with a dot markup version). Uses only LOOP and BLOCK. Tries to limit the extent of BLOCK. Run for now as an optional phase even if not targeting Wasm, to do some stress testing. Contributes to dotnet#121178

AndyAyersMS · 2025-11-06T19:54:13Z

FYI @dotnet/jit-contrib @SingleAccretion a first cut at wasm control flow. Eventually the text emission will end up being part of emitwasm (and in binary, with text disasm) and not part of this phase.

Left: sample control flow graph. Black are Wasm blocks, red are Wasm loops.

Right: sample Wasm instruction stream (block contents not shown, just BBxx).

	BB01 FALLTHROUGH BLOCK (13) BLOCK (12) BLOCK (8) BLOCK (4) BB04 BR_IF 0 (4) FALLTHROUGH LOOP (4) BB33 BR_IF 2 (8) FALLTHROUGH BB07 BR_IF 0 (2)be FALLTHROUGH END (4) LOOP END (4) BLOCK (7) BB09 BR_IF 0 (7) FALLTHROUGH BB10 BR_IF 1 (8) FALLTHROUGH BB12 FALLTHROUGH END (7) BB19 BR 1 (12) END (8) BB21 BB22 FALLTHROUGH BB16 FALLTHROUGH-inv BR_IF-inv 1 (13) BB30 FALLTHROUGH END (12) BB02 RETURN END (13) BB29 THROW

AndyAyersMS · 2025-11-06T20:08:29Z

The

FALLTHROUGH-inv
BR_IF-inv 1 (13)

above is a reminder we need to invert the branch condition (not yet done).

AndyAyersMS · 2025-11-06T23:48:49Z

Think this is ready for review. There could still be bugs in the control flow, but hard to be sure until we can actually generate code.

Errors seem to be all known or timeouts.

Copilot

Pull Request Overview

This PR adds a new experimental Wasm control flow simulation phase to the JIT compiler. The phase analyzes the control flow graph and simulates how Wasm BLOCK/END and LOOP/END control structures would be emitted for the method being compiled.

Introduces a new fgWasmControlFlow phase that transforms the control flow graph into Wasm-style nested control structures
Adds a JitWasmControlFlow configuration option to enable/disable this experimental feature (DEBUG builds only)
Implements an interval-based algorithm to properly nest blocks and loops according to Wasm requirements

Reviewed Changes

Copilot reviewed 7 out of 7 changed files in this pull request and generated 6 comments.

Show a summary per file

File	Description
src/coreclr/jit/jitconfigvalues.h	Adds the JitWasmControlFlow configuration integer to control the new phase
src/coreclr/jit/fgwasm.cpp	New file implementing the Wasm control flow analysis and simulation algorithm
src/coreclr/jit/compphases.h	Registers the PHASE_WASM_CONTROL_FLOW phase
src/coreclr/jit/compmemkind.h	Adds CMK_Wasm memory kind for allocations
src/coreclr/jit/compiler.h	Declares the fgWasmControlFlow method
src/coreclr/jit/compiler.cpp	Invokes the new phase conditionally in DEBUG builds after loop alignment
src/coreclr/jit/CMakeLists.txt	Adds fgwasm.cpp to the build sources

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

AndyAyersMS · 2025-11-07T15:31:16Z

@dotnet/jit-contrib PTAL

dotnet-policy-service · 2025-11-07T21:57:47Z

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

AndyAyersMS · 2025-11-10T15:34:08Z

@dotnet/jit-contrib ping

kg · 2025-11-11T23:38:11Z

LGTM but I'll leave the green check to someone who knows the JIT better

AndyAyersMS · 2025-11-12T00:13:53Z

I should do a run where I enable this in release just to see the TP impact... will do that locally and report back.

AndyAyersMS · 2025-11-13T21:06:06Z

I should do a run where I enable this in release just to see the TP impact... will do that locally and report back.

Enabling this in release, it has about a 0.5-0.9% TP hit. Worst-case was benchmaks.pgo at 0.92.

Restricting the analysis to running just on methods with optimization (as it will be doing mostly, R2R code is optimized) drops this to 0.55%.

Breaking it down by stages

DFS 0.14%
+ Loops 0.22%
+ LaRPO 0.27%
+ Intervals 0.36%
+ Conflicts 0.50%
+ Sort 0.53%
+ "codegen" 0.55%

so no clear bottleneck.

AndyAyersMS · 2025-11-14T17:44:47Z

The new phase is now disabled. I will create a wasm test pipeline where we can enable this.

AndyAyersMS · 2025-11-14T20:59:38Z

/ba-g one test failed with Half-way through waiting for remote process. Memory load: 18

Unrelated

Loops for Wasm control flow codegen don't involve EH or runtime mediated control flow transfers. Implement a custom block successor enumerator for Wasm, and adjust `fgRunDFS` to allow using this and also to generalize how the DFS is initiated. Use this to build a "Wasm" DFS. In that DFS handle both the main method and all funclets (by specifying funclet entries as additional DFS starting points). Update the loop finding code to make suitable changes when it is driven from a "Wasm" DFS instead of the typical all successor / all predecessor DFS. Remove the restriction in the Wasm control flow codegen that only handles the main method; now it works for the main method and all funclets. Contributes to #121178. Dependent on #121417. --------- Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

AndyAyersMS · 2025-11-06T19:39:33Z

Determine how to emit Wasm control flow from the JIT's control flow graph.

Relies on loop-aware RPO to determine the block order. Currently only handles the main method. Assumes irreducible loops have been fixed upstream (which is not yet guaranteed; bails out if not so).

Doesn't actually do any emission, just prints a textual description in the JIT dump (along with a dot markup version).

Uses only LOOP and BLOCK. Tries to limit the extent of BLOCK.

Run for now as an optional phase even if not targeting Wasm, to do some stress testing.

Contributes to #121178

Determine how to emit Wasm control flow from the JIT's control flow graph. Relies on loop-aware RPO to determine the block order. Currently only handles the main method. Assumes irreducible loops have been fixed upstream (which is not yet guaranteed; bails out if not so). Doesn't actually do any emission, just prints a textual description in the JIT dump (along with a dot markup version). Uses only LOOP and BLOCK. Tries to limit the extent of BLOCK. Run for now as an optional phase even if not targeting Wasm, to do some stress testing. Contributes to dotnet#121178

AndyAyersMS · 2025-11-06T19:54:13Z

FYI @dotnet/jit-contrib @SingleAccretion a first cut at wasm control flow. Eventually the text emission will end up being part of emitwasm (and in binary, with text disasm) and not part of this phase.

Left: sample control flow graph. Black are Wasm blocks, red are Wasm loops.

Right: sample Wasm instruction stream (block contents not shown, just BBxx).

	BB01 FALLTHROUGH BLOCK (13) BLOCK (12) BLOCK (8) BLOCK (4) BB04 BR_IF 0 (4) FALLTHROUGH LOOP (4) BB33 BR_IF 2 (8) FALLTHROUGH BB07 BR_IF 0 (2)be FALLTHROUGH END (4) LOOP END (4) BLOCK (7) BB09 BR_IF 0 (7) FALLTHROUGH BB10 BR_IF 1 (8) FALLTHROUGH BB12 FALLTHROUGH END (7) BB19 BR 1 (12) END (8) BB21 BB22 FALLTHROUGH BB16 FALLTHROUGH-inv BR_IF-inv 1 (13) BB30 FALLTHROUGH END (12) BB02 RETURN END (13) BB29 THROW

AndyAyersMS · 2025-11-06T20:08:29Z

The

FALLTHROUGH-inv
BR_IF-inv 1 (13)

above is a reminder we need to invert the branch condition (not yet done).

AndyAyersMS · 2025-11-06T23:48:49Z

Think this is ready for review. There could still be bugs in the control flow, but hard to be sure until we can actually generate code.

Errors seem to be all known or timeouts.

Copilot

Pull Request Overview

This PR adds a new experimental Wasm control flow simulation phase to the JIT compiler. The phase analyzes the control flow graph and simulates how Wasm BLOCK/END and LOOP/END control structures would be emitted for the method being compiled.

Introduces a new fgWasmControlFlow phase that transforms the control flow graph into Wasm-style nested control structures
Adds a JitWasmControlFlow configuration option to enable/disable this experimental feature (DEBUG builds only)
Implements an interval-based algorithm to properly nest blocks and loops according to Wasm requirements

Reviewed Changes

Copilot reviewed 7 out of 7 changed files in this pull request and generated 6 comments.

Show a summary per file

File	Description
src/coreclr/jit/jitconfigvalues.h	Adds the JitWasmControlFlow configuration integer to control the new phase
src/coreclr/jit/fgwasm.cpp	New file implementing the Wasm control flow analysis and simulation algorithm
src/coreclr/jit/compphases.h	Registers the PHASE_WASM_CONTROL_FLOW phase
src/coreclr/jit/compmemkind.h	Adds CMK_Wasm memory kind for allocations
src/coreclr/jit/compiler.h	Declares the fgWasmControlFlow method
src/coreclr/jit/compiler.cpp	Invokes the new phase conditionally in DEBUG builds after loop alignment
src/coreclr/jit/CMakeLists.txt	Adds fgwasm.cpp to the build sources

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

AndyAyersMS · 2025-11-07T15:31:16Z

@dotnet/jit-contrib PTAL

dotnet-policy-service · 2025-11-07T21:57:47Z

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

AndyAyersMS · 2025-11-10T15:34:08Z

@dotnet/jit-contrib ping

kg · 2025-11-11T23:38:11Z

LGTM but I'll leave the green check to someone who knows the JIT better

AndyAyersMS · 2025-11-12T00:13:53Z

I should do a run where I enable this in release just to see the TP impact... will do that locally and report back.

AndyAyersMS · 2025-11-13T21:06:06Z

I should do a run where I enable this in release just to see the TP impact... will do that locally and report back.

Enabling this in release, it has about a 0.5-0.9% TP hit. Worst-case was benchmaks.pgo at 0.92.

Restricting the analysis to running just on methods with optimization (as it will be doing mostly, R2R code is optimized) drops this to 0.55%.

Breaking it down by stages

DFS 0.14%
+ Loops 0.22%
+ LaRPO 0.27%
+ Intervals 0.36%
+ Conflicts 0.50%
+ Sort 0.53%
+ "codegen" 0.55%

so no clear bottleneck.

AndyAyersMS · 2025-11-14T17:44:47Z

The new phase is now disabled. I will create a wasm test pipeline where we can enable this.

AndyAyersMS · 2025-11-14T20:59:38Z

/ba-g one test failed with Half-way through waiting for remote process. Memory load: 18

Unrelated

Loops for Wasm control flow codegen don't involve EH or runtime mediated control flow transfers. Implement a custom block successor enumerator for Wasm, and adjust `fgRunDFS` to allow using this and also to generalize how the DFS is initiated. Use this to build a "Wasm" DFS. In that DFS handle both the main method and all funclets (by specifying funclet entries as additional DFS starting points). Update the loop finding code to make suitable changes when it is driven from a "Wasm" DFS instead of the typical all successor / all predecessor DFS. Remove the restriction in the Wasm control flow codegen that only handles the main method; now it works for the main method and all funclets. Contributes to #121178. Dependent on #121417. --------- Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

AndyAyersMS · 2025-11-06T19:39:33Z

Determine how to emit Wasm control flow from the JIT's control flow graph.

Relies on loop-aware RPO to determine the block order. Currently only handles the main method. Assumes irreducible loops have been fixed upstream (which is not yet guaranteed; bails out if not so).

Doesn't actually do any emission, just prints a textual description in the JIT dump (along with a dot markup version).

Uses only LOOP and BLOCK. Tries to limit the extent of BLOCK.

Run for now as an optional phase even if not targeting Wasm, to do some stress testing.

Contributes to #121178

Determine how to emit Wasm control flow from the JIT's control flow graph. Relies on loop-aware RPO to determine the block order. Currently only handles the main method. Assumes irreducible loops have been fixed upstream (which is not yet guaranteed; bails out if not so). Doesn't actually do any emission, just prints a textual description in the JIT dump (along with a dot markup version). Uses only LOOP and BLOCK. Tries to limit the extent of BLOCK. Run for now as an optional phase even if not targeting Wasm, to do some stress testing. Contributes to dotnet#121178

AndyAyersMS · 2025-11-06T19:54:13Z

FYI @dotnet/jit-contrib @SingleAccretion a first cut at wasm control flow. Eventually the text emission will end up being part of emitwasm (and in binary, with text disasm) and not part of this phase.

Left: sample control flow graph. Black are Wasm blocks, red are Wasm loops.

Right: sample Wasm instruction stream (block contents not shown, just BBxx).

	BB01 FALLTHROUGH BLOCK (13) BLOCK (12) BLOCK (8) BLOCK (4) BB04 BR_IF 0 (4) FALLTHROUGH LOOP (4) BB33 BR_IF 2 (8) FALLTHROUGH BB07 BR_IF 0 (2)be FALLTHROUGH END (4) LOOP END (4) BLOCK (7) BB09 BR_IF 0 (7) FALLTHROUGH BB10 BR_IF 1 (8) FALLTHROUGH BB12 FALLTHROUGH END (7) BB19 BR 1 (12) END (8) BB21 BB22 FALLTHROUGH BB16 FALLTHROUGH-inv BR_IF-inv 1 (13) BB30 FALLTHROUGH END (12) BB02 RETURN END (13) BB29 THROW

AndyAyersMS · 2025-11-06T20:08:29Z

The

FALLTHROUGH-inv
BR_IF-inv 1 (13)

above is a reminder we need to invert the branch condition (not yet done).

AndyAyersMS · 2025-11-06T23:48:49Z

Think this is ready for review. There could still be bugs in the control flow, but hard to be sure until we can actually generate code.

Errors seem to be all known or timeouts.

Copilot

Pull Request Overview

This PR adds a new experimental Wasm control flow simulation phase to the JIT compiler. The phase analyzes the control flow graph and simulates how Wasm BLOCK/END and LOOP/END control structures would be emitted for the method being compiled.

Introduces a new fgWasmControlFlow phase that transforms the control flow graph into Wasm-style nested control structures
Adds a JitWasmControlFlow configuration option to enable/disable this experimental feature (DEBUG builds only)
Implements an interval-based algorithm to properly nest blocks and loops according to Wasm requirements

Reviewed Changes

Copilot reviewed 7 out of 7 changed files in this pull request and generated 6 comments.

Show a summary per file

File	Description
src/coreclr/jit/jitconfigvalues.h	Adds the JitWasmControlFlow configuration integer to control the new phase
src/coreclr/jit/fgwasm.cpp	New file implementing the Wasm control flow analysis and simulation algorithm
src/coreclr/jit/compphases.h	Registers the PHASE_WASM_CONTROL_FLOW phase
src/coreclr/jit/compmemkind.h	Adds CMK_Wasm memory kind for allocations
src/coreclr/jit/compiler.h	Declares the fgWasmControlFlow method
src/coreclr/jit/compiler.cpp	Invokes the new phase conditionally in DEBUG builds after loop alignment
src/coreclr/jit/CMakeLists.txt	Adds fgwasm.cpp to the build sources

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

AndyAyersMS · 2025-11-07T15:31:16Z

@dotnet/jit-contrib PTAL

dotnet-policy-service · 2025-11-07T21:57:47Z

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

AndyAyersMS · 2025-11-10T15:34:08Z

@dotnet/jit-contrib ping

kg · 2025-11-11T23:38:11Z

LGTM but I'll leave the green check to someone who knows the JIT better

AndyAyersMS · 2025-11-12T00:13:53Z

I should do a run where I enable this in release just to see the TP impact... will do that locally and report back.

AndyAyersMS · 2025-11-13T21:06:06Z

I should do a run where I enable this in release just to see the TP impact... will do that locally and report back.

Enabling this in release, it has about a 0.5-0.9% TP hit. Worst-case was benchmaks.pgo at 0.92.

Restricting the analysis to running just on methods with optimization (as it will be doing mostly, R2R code is optimized) drops this to 0.55%.

Breaking it down by stages

DFS 0.14%
+ Loops 0.22%
+ LaRPO 0.27%
+ Intervals 0.36%
+ Conflicts 0.50%
+ Sort 0.53%
+ "codegen" 0.55%

so no clear bottleneck.

AndyAyersMS · 2025-11-14T17:44:47Z

The new phase is now disabled. I will create a wasm test pipeline where we can enable this.

AndyAyersMS · 2025-11-14T20:59:38Z

/ba-g one test failed with Half-way through waiting for remote process. Memory load: 18

Unrelated

Loops for Wasm control flow codegen don't involve EH or runtime mediated control flow transfers. Implement a custom block successor enumerator for Wasm, and adjust `fgRunDFS` to allow using this and also to generalize how the DFS is initiated. Use this to build a "Wasm" DFS. In that DFS handle both the main method and all funclets (by specifying funclet entries as additional DFS starting points). Update the loop finding code to make suitable changes when it is driven from a "Wasm" DFS instead of the typical all successor / all predecessor DFS. Remove the restriction in the Wasm control flow codegen that only handles the main method; now it works for the main method and all funclets. Contributes to #121178. Dependent on #121417. --------- Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

AndyAyersMS · 2025-11-06T19:39:33Z

Determine how to emit Wasm control flow from the JIT's control flow graph.

Relies on loop-aware RPO to determine the block order. Currently only handles the main method. Assumes irreducible loops have been fixed upstream (which is not yet guaranteed; bails out if not so).

Doesn't actually do any emission, just prints a textual description in the JIT dump (along with a dot markup version).

Uses only LOOP and BLOCK. Tries to limit the extent of BLOCK.

Run for now as an optional phase even if not targeting Wasm, to do some stress testing.

Contributes to #121178

Determine how to emit Wasm control flow from the JIT's control flow graph. Relies on loop-aware RPO to determine the block order. Currently only handles the main method. Assumes irreducible loops have been fixed upstream (which is not yet guaranteed; bails out if not so). Doesn't actually do any emission, just prints a textual description in the JIT dump (along with a dot markup version). Uses only LOOP and BLOCK. Tries to limit the extent of BLOCK. Run for now as an optional phase even if not targeting Wasm, to do some stress testing. Contributes to dotnet#121178

AndyAyersMS · 2025-11-06T19:54:13Z

FYI @dotnet/jit-contrib @SingleAccretion a first cut at wasm control flow. Eventually the text emission will end up being part of emitwasm (and in binary, with text disasm) and not part of this phase.

Left: sample control flow graph. Black are Wasm blocks, red are Wasm loops.

Right: sample Wasm instruction stream (block contents not shown, just BBxx).

	BB01 FALLTHROUGH BLOCK (13) BLOCK (12) BLOCK (8) BLOCK (4) BB04 BR_IF 0 (4) FALLTHROUGH LOOP (4) BB33 BR_IF 2 (8) FALLTHROUGH BB07 BR_IF 0 (2)be FALLTHROUGH END (4) LOOP END (4) BLOCK (7) BB09 BR_IF 0 (7) FALLTHROUGH BB10 BR_IF 1 (8) FALLTHROUGH BB12 FALLTHROUGH END (7) BB19 BR 1 (12) END (8) BB21 BB22 FALLTHROUGH BB16 FALLTHROUGH-inv BR_IF-inv 1 (13) BB30 FALLTHROUGH END (12) BB02 RETURN END (13) BB29 THROW

AndyAyersMS · 2025-11-06T20:08:29Z

The

FALLTHROUGH-inv
BR_IF-inv 1 (13)

above is a reminder we need to invert the branch condition (not yet done).

AndyAyersMS · 2025-11-06T23:48:49Z

Think this is ready for review. There could still be bugs in the control flow, but hard to be sure until we can actually generate code.

Errors seem to be all known or timeouts.

Copilot

Pull Request Overview

This PR adds a new experimental Wasm control flow simulation phase to the JIT compiler. The phase analyzes the control flow graph and simulates how Wasm BLOCK/END and LOOP/END control structures would be emitted for the method being compiled.

Introduces a new fgWasmControlFlow phase that transforms the control flow graph into Wasm-style nested control structures
Adds a JitWasmControlFlow configuration option to enable/disable this experimental feature (DEBUG builds only)
Implements an interval-based algorithm to properly nest blocks and loops according to Wasm requirements

Reviewed Changes

Copilot reviewed 7 out of 7 changed files in this pull request and generated 6 comments.

Show a summary per file

File	Description
src/coreclr/jit/jitconfigvalues.h	Adds the JitWasmControlFlow configuration integer to control the new phase
src/coreclr/jit/fgwasm.cpp	New file implementing the Wasm control flow analysis and simulation algorithm
src/coreclr/jit/compphases.h	Registers the PHASE_WASM_CONTROL_FLOW phase
src/coreclr/jit/compmemkind.h	Adds CMK_Wasm memory kind for allocations
src/coreclr/jit/compiler.h	Declares the fgWasmControlFlow method
src/coreclr/jit/compiler.cpp	Invokes the new phase conditionally in DEBUG builds after loop alignment
src/coreclr/jit/CMakeLists.txt	Adds fgwasm.cpp to the build sources

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

AndyAyersMS · 2025-11-07T15:31:16Z

@dotnet/jit-contrib PTAL

dotnet-policy-service · 2025-11-07T21:57:47Z

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

AndyAyersMS · 2025-11-10T15:34:08Z

@dotnet/jit-contrib ping

kg · 2025-11-11T23:38:11Z

LGTM but I'll leave the green check to someone who knows the JIT better

AndyAyersMS · 2025-11-12T00:13:53Z

I should do a run where I enable this in release just to see the TP impact... will do that locally and report back.

AndyAyersMS · 2025-11-13T21:06:06Z

I should do a run where I enable this in release just to see the TP impact... will do that locally and report back.

Enabling this in release, it has about a 0.5-0.9% TP hit. Worst-case was benchmaks.pgo at 0.92.

Restricting the analysis to running just on methods with optimization (as it will be doing mostly, R2R code is optimized) drops this to 0.55%.

Breaking it down by stages

DFS 0.14%
+ Loops 0.22%
+ LaRPO 0.27%
+ Intervals 0.36%
+ Conflicts 0.50%
+ Sort 0.53%
+ "codegen" 0.55%

so no clear bottleneck.

AndyAyersMS · 2025-11-14T17:44:47Z

The new phase is now disabled. I will create a wasm test pipeline where we can enable this.

AndyAyersMS · 2025-11-14T20:59:38Z

/ba-g one test failed with Half-way through waiting for remote process. Memory load: 18

Unrelated

Loops for Wasm control flow codegen don't involve EH or runtime mediated control flow transfers. Implement a custom block successor enumerator for Wasm, and adjust `fgRunDFS` to allow using this and also to generalize how the DFS is initiated. Use this to build a "Wasm" DFS. In that DFS handle both the main method and all funclets (by specifying funclet entries as additional DFS starting points). Update the loop finding code to make suitable changes when it is driven from a "Wasm" DFS instead of the typical all successor / all predecessor DFS. Remove the restriction in the Wasm control flow codegen that only handles the main method; now it works for the main method and all funclets. Contributes to #121178. Dependent on #121417. --------- Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

AndyAyersMS · 2025-11-06T19:39:33Z

Determine how to emit Wasm control flow from the JIT's control flow graph.

Relies on loop-aware RPO to determine the block order. Currently only handles the main method. Assumes irreducible loops have been fixed upstream (which is not yet guaranteed; bails out if not so).

Doesn't actually do any emission, just prints a textual description in the JIT dump (along with a dot markup version).

Uses only LOOP and BLOCK. Tries to limit the extent of BLOCK.

Run for now as an optional phase even if not targeting Wasm, to do some stress testing.

Contributes to #121178

Determine how to emit Wasm control flow from the JIT's control flow graph. Relies on loop-aware RPO to determine the block order. Currently only handles the main method. Assumes irreducible loops have been fixed upstream (which is not yet guaranteed; bails out if not so). Doesn't actually do any emission, just prints a textual description in the JIT dump (along with a dot markup version). Uses only LOOP and BLOCK. Tries to limit the extent of BLOCK. Run for now as an optional phase even if not targeting Wasm, to do some stress testing. Contributes to dotnet#121178

AndyAyersMS · 2025-11-06T19:54:13Z

FYI @dotnet/jit-contrib @SingleAccretion a first cut at wasm control flow. Eventually the text emission will end up being part of emitwasm (and in binary, with text disasm) and not part of this phase.

Left: sample control flow graph. Black are Wasm blocks, red are Wasm loops.

Right: sample Wasm instruction stream (block contents not shown, just BBxx).

	BB01 FALLTHROUGH BLOCK (13) BLOCK (12) BLOCK (8) BLOCK (4) BB04 BR_IF 0 (4) FALLTHROUGH LOOP (4) BB33 BR_IF 2 (8) FALLTHROUGH BB07 BR_IF 0 (2)be FALLTHROUGH END (4) LOOP END (4) BLOCK (7) BB09 BR_IF 0 (7) FALLTHROUGH BB10 BR_IF 1 (8) FALLTHROUGH BB12 FALLTHROUGH END (7) BB19 BR 1 (12) END (8) BB21 BB22 FALLTHROUGH BB16 FALLTHROUGH-inv BR_IF-inv 1 (13) BB30 FALLTHROUGH END (12) BB02 RETURN END (13) BB29 THROW

AndyAyersMS · 2025-11-06T20:08:29Z

The

FALLTHROUGH-inv
BR_IF-inv 1 (13)

above is a reminder we need to invert the branch condition (not yet done).

AndyAyersMS · 2025-11-06T23:48:49Z

Think this is ready for review. There could still be bugs in the control flow, but hard to be sure until we can actually generate code.

Errors seem to be all known or timeouts.

Copilot

Pull Request Overview

This PR adds a new experimental Wasm control flow simulation phase to the JIT compiler. The phase analyzes the control flow graph and simulates how Wasm BLOCK/END and LOOP/END control structures would be emitted for the method being compiled.

Introduces a new fgWasmControlFlow phase that transforms the control flow graph into Wasm-style nested control structures
Adds a JitWasmControlFlow configuration option to enable/disable this experimental feature (DEBUG builds only)
Implements an interval-based algorithm to properly nest blocks and loops according to Wasm requirements

Reviewed Changes

Copilot reviewed 7 out of 7 changed files in this pull request and generated 6 comments.

Show a summary per file

File	Description
src/coreclr/jit/jitconfigvalues.h	Adds the JitWasmControlFlow configuration integer to control the new phase
src/coreclr/jit/fgwasm.cpp	New file implementing the Wasm control flow analysis and simulation algorithm
src/coreclr/jit/compphases.h	Registers the PHASE_WASM_CONTROL_FLOW phase
src/coreclr/jit/compmemkind.h	Adds CMK_Wasm memory kind for allocations
src/coreclr/jit/compiler.h	Declares the fgWasmControlFlow method
src/coreclr/jit/compiler.cpp	Invokes the new phase conditionally in DEBUG builds after loop alignment
src/coreclr/jit/CMakeLists.txt	Adds fgwasm.cpp to the build sources

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

AndyAyersMS · 2025-11-07T15:31:16Z

@dotnet/jit-contrib PTAL

dotnet-policy-service · 2025-11-07T21:57:47Z

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

AndyAyersMS · 2025-11-10T15:34:08Z

@dotnet/jit-contrib ping

kg · 2025-11-11T23:38:11Z

LGTM but I'll leave the green check to someone who knows the JIT better

AndyAyersMS · 2025-11-12T00:13:53Z

I should do a run where I enable this in release just to see the TP impact... will do that locally and report back.

AndyAyersMS · 2025-11-13T21:06:06Z

I should do a run where I enable this in release just to see the TP impact... will do that locally and report back.

Enabling this in release, it has about a 0.5-0.9% TP hit. Worst-case was benchmaks.pgo at 0.92.

Restricting the analysis to running just on methods with optimization (as it will be doing mostly, R2R code is optimized) drops this to 0.55%.

Breaking it down by stages

DFS 0.14%
+ Loops 0.22%
+ LaRPO 0.27%
+ Intervals 0.36%
+ Conflicts 0.50%
+ Sort 0.53%
+ "codegen" 0.55%

so no clear bottleneck.

AndyAyersMS · 2025-11-14T17:44:47Z

The new phase is now disabled. I will create a wasm test pipeline where we can enable this.

AndyAyersMS · 2025-11-14T20:59:38Z

/ba-g one test failed with Half-way through waiting for remote process. Memory load: 18

Unrelated

Loops for Wasm control flow codegen don't involve EH or runtime mediated control flow transfers. Implement a custom block successor enumerator for Wasm, and adjust `fgRunDFS` to allow using this and also to generalize how the DFS is initiated. Use this to build a "Wasm" DFS. In that DFS handle both the main method and all funclets (by specifying funclet entries as additional DFS starting points). Update the loop finding code to make suitable changes when it is driven from a "Wasm" DFS instead of the typical all successor / all predecessor DFS. Remove the restriction in the Wasm control flow codegen that only handles the main method; now it works for the main method and all funclets. Contributes to #121178. Dependent on #121417. --------- Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

AndyAyersMS · 2025-11-06T19:39:33Z

Determine how to emit Wasm control flow from the JIT's control flow graph.

Relies on loop-aware RPO to determine the block order. Currently only handles the main method. Assumes irreducible loops have been fixed upstream (which is not yet guaranteed; bails out if not so).

Doesn't actually do any emission, just prints a textual description in the JIT dump (along with a dot markup version).

Uses only LOOP and BLOCK. Tries to limit the extent of BLOCK.

Run for now as an optional phase even if not targeting Wasm, to do some stress testing.

Contributes to #121178

Determine how to emit Wasm control flow from the JIT's control flow graph. Relies on loop-aware RPO to determine the block order. Currently only handles the main method. Assumes irreducible loops have been fixed upstream (which is not yet guaranteed; bails out if not so). Doesn't actually do any emission, just prints a textual description in the JIT dump (along with a dot markup version). Uses only LOOP and BLOCK. Tries to limit the extent of BLOCK. Run for now as an optional phase even if not targeting Wasm, to do some stress testing. Contributes to dotnet#121178

AndyAyersMS · 2025-11-06T19:54:13Z

FYI @dotnet/jit-contrib @SingleAccretion a first cut at wasm control flow. Eventually the text emission will end up being part of emitwasm (and in binary, with text disasm) and not part of this phase.

Left: sample control flow graph. Black are Wasm blocks, red are Wasm loops.

Right: sample Wasm instruction stream (block contents not shown, just BBxx).

	BB01 FALLTHROUGH BLOCK (13) BLOCK (12) BLOCK (8) BLOCK (4) BB04 BR_IF 0 (4) FALLTHROUGH LOOP (4) BB33 BR_IF 2 (8) FALLTHROUGH BB07 BR_IF 0 (2)be FALLTHROUGH END (4) LOOP END (4) BLOCK (7) BB09 BR_IF 0 (7) FALLTHROUGH BB10 BR_IF 1 (8) FALLTHROUGH BB12 FALLTHROUGH END (7) BB19 BR 1 (12) END (8) BB21 BB22 FALLTHROUGH BB16 FALLTHROUGH-inv BR_IF-inv 1 (13) BB30 FALLTHROUGH END (12) BB02 RETURN END (13) BB29 THROW

AndyAyersMS · 2025-11-06T20:08:29Z

The

FALLTHROUGH-inv
BR_IF-inv 1 (13)

above is a reminder we need to invert the branch condition (not yet done).

AndyAyersMS · 2025-11-06T23:48:49Z

Think this is ready for review. There could still be bugs in the control flow, but hard to be sure until we can actually generate code.

Errors seem to be all known or timeouts.

Copilot

Pull Request Overview

This PR adds a new experimental Wasm control flow simulation phase to the JIT compiler. The phase analyzes the control flow graph and simulates how Wasm BLOCK/END and LOOP/END control structures would be emitted for the method being compiled.

Introduces a new fgWasmControlFlow phase that transforms the control flow graph into Wasm-style nested control structures
Adds a JitWasmControlFlow configuration option to enable/disable this experimental feature (DEBUG builds only)
Implements an interval-based algorithm to properly nest blocks and loops according to Wasm requirements

Reviewed Changes

Copilot reviewed 7 out of 7 changed files in this pull request and generated 6 comments.

Show a summary per file

File	Description
src/coreclr/jit/jitconfigvalues.h	Adds the JitWasmControlFlow configuration integer to control the new phase
src/coreclr/jit/fgwasm.cpp	New file implementing the Wasm control flow analysis and simulation algorithm
src/coreclr/jit/compphases.h	Registers the PHASE_WASM_CONTROL_FLOW phase
src/coreclr/jit/compmemkind.h	Adds CMK_Wasm memory kind for allocations
src/coreclr/jit/compiler.h	Declares the fgWasmControlFlow method
src/coreclr/jit/compiler.cpp	Invokes the new phase conditionally in DEBUG builds after loop alignment
src/coreclr/jit/CMakeLists.txt	Adds fgwasm.cpp to the build sources

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

AndyAyersMS · 2025-11-07T15:31:16Z

@dotnet/jit-contrib PTAL

dotnet-policy-service · 2025-11-07T21:57:47Z

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

AndyAyersMS · 2025-11-10T15:34:08Z

@dotnet/jit-contrib ping

kg · 2025-11-11T23:38:11Z

LGTM but I'll leave the green check to someone who knows the JIT better

AndyAyersMS · 2025-11-12T00:13:53Z

I should do a run where I enable this in release just to see the TP impact... will do that locally and report back.

AndyAyersMS · 2025-11-13T21:06:06Z

I should do a run where I enable this in release just to see the TP impact... will do that locally and report back.

Enabling this in release, it has about a 0.5-0.9% TP hit. Worst-case was benchmaks.pgo at 0.92.

Restricting the analysis to running just on methods with optimization (as it will be doing mostly, R2R code is optimized) drops this to 0.55%.

Breaking it down by stages

DFS 0.14%
+ Loops 0.22%
+ LaRPO 0.27%
+ Intervals 0.36%
+ Conflicts 0.50%
+ Sort 0.53%
+ "codegen" 0.55%

so no clear bottleneck.

AndyAyersMS · 2025-11-14T17:44:47Z

The new phase is now disabled. I will create a wasm test pipeline where we can enable this.

AndyAyersMS · 2025-11-14T20:59:38Z

/ba-g one test failed with Half-way through waiting for remote process. Memory load: 18

Unrelated

Loops for Wasm control flow codegen don't involve EH or runtime mediated control flow transfers. Implement a custom block successor enumerator for Wasm, and adjust `fgRunDFS` to allow using this and also to generalize how the DFS is initiated. Use this to build a "Wasm" DFS. In that DFS handle both the main method and all funclets (by specifying funclet entries as additional DFS starting points). Update the loop finding code to make suitable changes when it is driven from a "Wasm" DFS instead of the typical all successor / all predecessor DFS. Remove the restriction in the Wasm control flow codegen that only handles the main method; now it works for the main method and all funclets. Contributes to #121178. Dependent on #121417. --------- Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

AndyAyersMS · 2025-11-06T19:39:33Z

Determine how to emit Wasm control flow from the JIT's control flow graph.

Relies on loop-aware RPO to determine the block order. Currently only handles the main method. Assumes irreducible loops have been fixed upstream (which is not yet guaranteed; bails out if not so).

Doesn't actually do any emission, just prints a textual description in the JIT dump (along with a dot markup version).

Uses only LOOP and BLOCK. Tries to limit the extent of BLOCK.

Run for now as an optional phase even if not targeting Wasm, to do some stress testing.

Contributes to #121178

Determine how to emit Wasm control flow from the JIT's control flow graph. Relies on loop-aware RPO to determine the block order. Currently only handles the main method. Assumes irreducible loops have been fixed upstream (which is not yet guaranteed; bails out if not so). Doesn't actually do any emission, just prints a textual description in the JIT dump (along with a dot markup version). Uses only LOOP and BLOCK. Tries to limit the extent of BLOCK. Run for now as an optional phase even if not targeting Wasm, to do some stress testing. Contributes to dotnet#121178

AndyAyersMS · 2025-11-06T19:54:13Z

FYI @dotnet/jit-contrib @SingleAccretion a first cut at wasm control flow. Eventually the text emission will end up being part of emitwasm (and in binary, with text disasm) and not part of this phase.

Left: sample control flow graph. Black are Wasm blocks, red are Wasm loops.

Right: sample Wasm instruction stream (block contents not shown, just BBxx).

	BB01 FALLTHROUGH BLOCK (13) BLOCK (12) BLOCK (8) BLOCK (4) BB04 BR_IF 0 (4) FALLTHROUGH LOOP (4) BB33 BR_IF 2 (8) FALLTHROUGH BB07 BR_IF 0 (2)be FALLTHROUGH END (4) LOOP END (4) BLOCK (7) BB09 BR_IF 0 (7) FALLTHROUGH BB10 BR_IF 1 (8) FALLTHROUGH BB12 FALLTHROUGH END (7) BB19 BR 1 (12) END (8) BB21 BB22 FALLTHROUGH BB16 FALLTHROUGH-inv BR_IF-inv 1 (13) BB30 FALLTHROUGH END (12) BB02 RETURN END (13) BB29 THROW

AndyAyersMS · 2025-11-06T20:08:29Z

The

FALLTHROUGH-inv
BR_IF-inv 1 (13)

above is a reminder we need to invert the branch condition (not yet done).

AndyAyersMS · 2025-11-06T23:48:49Z

Think this is ready for review. There could still be bugs in the control flow, but hard to be sure until we can actually generate code.

Errors seem to be all known or timeouts.

Copilot

Pull Request Overview

This PR adds a new experimental Wasm control flow simulation phase to the JIT compiler. The phase analyzes the control flow graph and simulates how Wasm BLOCK/END and LOOP/END control structures would be emitted for the method being compiled.

Introduces a new fgWasmControlFlow phase that transforms the control flow graph into Wasm-style nested control structures
Adds a JitWasmControlFlow configuration option to enable/disable this experimental feature (DEBUG builds only)
Implements an interval-based algorithm to properly nest blocks and loops according to Wasm requirements

Reviewed Changes

Copilot reviewed 7 out of 7 changed files in this pull request and generated 6 comments.

Show a summary per file

File	Description
src/coreclr/jit/jitconfigvalues.h	Adds the JitWasmControlFlow configuration integer to control the new phase
src/coreclr/jit/fgwasm.cpp	New file implementing the Wasm control flow analysis and simulation algorithm
src/coreclr/jit/compphases.h	Registers the PHASE_WASM_CONTROL_FLOW phase
src/coreclr/jit/compmemkind.h	Adds CMK_Wasm memory kind for allocations
src/coreclr/jit/compiler.h	Declares the fgWasmControlFlow method
src/coreclr/jit/compiler.cpp	Invokes the new phase conditionally in DEBUG builds after loop alignment
src/coreclr/jit/CMakeLists.txt	Adds fgwasm.cpp to the build sources

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

AndyAyersMS · 2025-11-07T15:31:16Z

@dotnet/jit-contrib PTAL

dotnet-policy-service · 2025-11-07T21:57:47Z

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

AndyAyersMS · 2025-11-10T15:34:08Z

@dotnet/jit-contrib ping

kg · 2025-11-11T23:38:11Z

LGTM but I'll leave the green check to someone who knows the JIT better

AndyAyersMS · 2025-11-12T00:13:53Z

I should do a run where I enable this in release just to see the TP impact... will do that locally and report back.

AndyAyersMS · 2025-11-13T21:06:06Z

I should do a run where I enable this in release just to see the TP impact... will do that locally and report back.

Enabling this in release, it has about a 0.5-0.9% TP hit. Worst-case was benchmaks.pgo at 0.92.

Restricting the analysis to running just on methods with optimization (as it will be doing mostly, R2R code is optimized) drops this to 0.55%.

Breaking it down by stages

DFS 0.14%
+ Loops 0.22%
+ LaRPO 0.27%
+ Intervals 0.36%
+ Conflicts 0.50%
+ Sort 0.53%
+ "codegen" 0.55%

so no clear bottleneck.

AndyAyersMS · 2025-11-14T17:44:47Z

The new phase is now disabled. I will create a wasm test pipeline where we can enable this.

AndyAyersMS · 2025-11-14T20:59:38Z

/ba-g one test failed with Half-way through waiting for remote process. Memory load: 18

Unrelated

Loops for Wasm control flow codegen don't involve EH or runtime mediated control flow transfers. Implement a custom block successor enumerator for Wasm, and adjust `fgRunDFS` to allow using this and also to generalize how the DFS is initiated. Use this to build a "Wasm" DFS. In that DFS handle both the main method and all funclets (by specifying funclet entries as additional DFS starting points). Update the loop finding code to make suitable changes when it is driven from a "Wasm" DFS instead of the typical all successor / all predecessor DFS. Remove the restriction in the Wasm control flow codegen that only handles the main method; now it works for the main method and all funclets. Contributes to #121178. Dependent on #121417. --------- Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

AndyAyersMS · 2025-11-06T19:39:33Z

Determine how to emit Wasm control flow from the JIT's control flow graph.

Relies on loop-aware RPO to determine the block order. Currently only handles the main method. Assumes irreducible loops have been fixed upstream (which is not yet guaranteed; bails out if not so).

Doesn't actually do any emission, just prints a textual description in the JIT dump (along with a dot markup version).

Uses only LOOP and BLOCK. Tries to limit the extent of BLOCK.

Run for now as an optional phase even if not targeting Wasm, to do some stress testing.

Contributes to #121178

Determine how to emit Wasm control flow from the JIT's control flow graph. Relies on loop-aware RPO to determine the block order. Currently only handles the main method. Assumes irreducible loops have been fixed upstream (which is not yet guaranteed; bails out if not so). Doesn't actually do any emission, just prints a textual description in the JIT dump (along with a dot markup version). Uses only LOOP and BLOCK. Tries to limit the extent of BLOCK. Run for now as an optional phase even if not targeting Wasm, to do some stress testing. Contributes to dotnet#121178

AndyAyersMS · 2025-11-06T19:54:13Z

FYI @dotnet/jit-contrib @SingleAccretion a first cut at wasm control flow. Eventually the text emission will end up being part of emitwasm (and in binary, with text disasm) and not part of this phase.

Left: sample control flow graph. Black are Wasm blocks, red are Wasm loops.

Right: sample Wasm instruction stream (block contents not shown, just BBxx).

	BB01 FALLTHROUGH BLOCK (13) BLOCK (12) BLOCK (8) BLOCK (4) BB04 BR_IF 0 (4) FALLTHROUGH LOOP (4) BB33 BR_IF 2 (8) FALLTHROUGH BB07 BR_IF 0 (2)be FALLTHROUGH END (4) LOOP END (4) BLOCK (7) BB09 BR_IF 0 (7) FALLTHROUGH BB10 BR_IF 1 (8) FALLTHROUGH BB12 FALLTHROUGH END (7) BB19 BR 1 (12) END (8) BB21 BB22 FALLTHROUGH BB16 FALLTHROUGH-inv BR_IF-inv 1 (13) BB30 FALLTHROUGH END (12) BB02 RETURN END (13) BB29 THROW

AndyAyersMS · 2025-11-06T20:08:29Z

The

FALLTHROUGH-inv
BR_IF-inv 1 (13)

above is a reminder we need to invert the branch condition (not yet done).

AndyAyersMS · 2025-11-06T23:48:49Z

Think this is ready for review. There could still be bugs in the control flow, but hard to be sure until we can actually generate code.

Errors seem to be all known or timeouts.

Copilot

Pull Request Overview

This PR adds a new experimental Wasm control flow simulation phase to the JIT compiler. The phase analyzes the control flow graph and simulates how Wasm BLOCK/END and LOOP/END control structures would be emitted for the method being compiled.

Introduces a new fgWasmControlFlow phase that transforms the control flow graph into Wasm-style nested control structures
Adds a JitWasmControlFlow configuration option to enable/disable this experimental feature (DEBUG builds only)
Implements an interval-based algorithm to properly nest blocks and loops according to Wasm requirements

Reviewed Changes

Copilot reviewed 7 out of 7 changed files in this pull request and generated 6 comments.

Show a summary per file

File	Description
src/coreclr/jit/jitconfigvalues.h	Adds the JitWasmControlFlow configuration integer to control the new phase
src/coreclr/jit/fgwasm.cpp	New file implementing the Wasm control flow analysis and simulation algorithm
src/coreclr/jit/compphases.h	Registers the PHASE_WASM_CONTROL_FLOW phase
src/coreclr/jit/compmemkind.h	Adds CMK_Wasm memory kind for allocations
src/coreclr/jit/compiler.h	Declares the fgWasmControlFlow method
src/coreclr/jit/compiler.cpp	Invokes the new phase conditionally in DEBUG builds after loop alignment
src/coreclr/jit/CMakeLists.txt	Adds fgwasm.cpp to the build sources

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

AndyAyersMS · 2025-11-07T15:31:16Z

@dotnet/jit-contrib PTAL

dotnet-policy-service · 2025-11-07T21:57:47Z

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

AndyAyersMS · 2025-11-10T15:34:08Z

@dotnet/jit-contrib ping

kg · 2025-11-11T23:38:11Z

LGTM but I'll leave the green check to someone who knows the JIT better

AndyAyersMS · 2025-11-12T00:13:53Z

I should do a run where I enable this in release just to see the TP impact... will do that locally and report back.

AndyAyersMS · 2025-11-13T21:06:06Z

I should do a run where I enable this in release just to see the TP impact... will do that locally and report back.

Enabling this in release, it has about a 0.5-0.9% TP hit. Worst-case was benchmaks.pgo at 0.92.

Restricting the analysis to running just on methods with optimization (as it will be doing mostly, R2R code is optimized) drops this to 0.55%.

Breaking it down by stages

DFS 0.14%
+ Loops 0.22%
+ LaRPO 0.27%
+ Intervals 0.36%
+ Conflicts 0.50%
+ Sort 0.53%
+ "codegen" 0.55%

so no clear bottleneck.

AndyAyersMS · 2025-11-14T17:44:47Z

The new phase is now disabled. I will create a wasm test pipeline where we can enable this.

AndyAyersMS · 2025-11-14T20:59:38Z

/ba-g one test failed with Half-way through waiting for remote process. Memory load: 18

Unrelated

Loops for Wasm control flow codegen don't involve EH or runtime mediated control flow transfers. Implement a custom block successor enumerator for Wasm, and adjust `fgRunDFS` to allow using this and also to generalize how the DFS is initiated. Use this to build a "Wasm" DFS. In that DFS handle both the main method and all funclets (by specifying funclet entries as additional DFS starting points). Update the loop finding code to make suitable changes when it is driven from a "Wasm" DFS instead of the typical all successor / all predecessor DFS. Remove the restriction in the Wasm control flow codegen that only handles the main method; now it works for the main method and all funclets. Contributes to #121178. Dependent on #121417. --------- Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

github-actionsBot added the area-CodeGen-coreclr CLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMI label Nov 6, 2025

dotnet-policy-serviceBot assigned AndyAyersMS Nov 6, 2025

fix release build
ca2c9b4

fix llvm build
39e0bd3

AndyAyersMS marked this pull request as ready for review November 6, 2025 23:48

CopilotAI review requested due to automatic review settings November 6, 2025 23:48

CopilotAI reviewed Nov 6, 2025
View reviewed changes

Comment threadsrc/coreclr/jit/fgwasm.cpp Outdated
Comment threadsrc/coreclr/jit/fgwasm.cpp Outdated
Comment threadsrc/coreclr/jit/fgwasm.cpp Outdated
Comment threadsrc/coreclr/jit/fgwasm.cpp Outdated
Comment threadsrc/coreclr/jit/fgwasm.cpp Outdated
Comment threadsrc/coreclr/jit/fgwasm.cpp Outdated

Fix typos
e8882ab
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

AndyAyersMS commented Nov 7, 2025
View reviewed changes

Comment threadsrc/coreclr/jit/fgwasm.cpp Outdated

Fix more typos
890548e

AndyAyersMS requested a review from a teamNovember 7, 2025 15:31

AndyAyersMS mentioned this pull request Nov 7, 2025
[Wasm RyuJIT] Implement Wasm DFS and Loop Finding #121457
Merged

am11 added the arch-wasm WebAssembly architecture label Nov 7, 2025

Merge branch 'main' into WasmControlFlowBasics
9f9e0a6

This was referenced Nov 11, 2025
slow macOS - "##[error]The job running on agent Azure Pipelines 9 ran longer than the maximum time of 60 minutes." dotnet/dnceng#1883
Open
AppHost test failure: I/O failure when writing extracted files #120653
Closed

jakobbotsch self-requested a review November 11, 2025 18:24

SingleAccretion reviewed Nov 11, 2025
View reviewed changes

jakobbotsch reviewed Nov 11, 2025
View reviewed changes

Comment threadsrc/coreclr/jit/fgwasm.cpp

jakobbotsch reviewed Nov 11, 2025
View reviewed changes

Comment threadsrc/coreclr/jit/fgwasm.cpp

kg reviewed Nov 11, 2025
View reviewed changes

Comment threadsrc/coreclr/jit/fgwasm.cpp

jakobbotsch approved these changes Nov 12, 2025
View reviewed changes

AndyAyersMS added 3 commits November 13, 2025 13:09

Merge branch 'main' into WasmControlFlowBasics
4a7bf9e

review feedback
9094aeb

disable by default
c282fa1

AndyAyersMS merged commit b435b40 into dotnet:mainNov 14, 2025
109 of 112 checks passed

dotnet-maestroBot mentioned this pull request Nov 19, 2025
[main] Source code updates from dotnet/runtime dotnet/dotnet#3448
Merged

AndyAyersMS mentioned this pull request Nov 19, 2025
[Wasm RyuJIT] Basic Control Flow #121178
Closed
12 tasks

github-actionsBot locked and limited conversation to collaborators Dec 15, 2025

github-actionsBot added the area-CodeGen-coreclr CLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMI label Nov 6, 2025

dotnet-policy-serviceBot assigned AndyAyersMS Nov 6, 2025

fix release build
ca2c9b4

fix llvm build
39e0bd3

AndyAyersMS marked this pull request as ready for review November 6, 2025 23:48

CopilotAI review requested due to automatic review settings November 6, 2025 23:48

CopilotAI reviewed Nov 6, 2025
View reviewed changes

Comment threadsrc/coreclr/jit/fgwasm.cpp Outdated
Comment threadsrc/coreclr/jit/fgwasm.cpp Outdated
Comment threadsrc/coreclr/jit/fgwasm.cpp Outdated
Comment threadsrc/coreclr/jit/fgwasm.cpp Outdated
Comment threadsrc/coreclr/jit/fgwasm.cpp Outdated
Comment threadsrc/coreclr/jit/fgwasm.cpp Outdated

Fix typos
e8882ab
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

AndyAyersMS commented Nov 7, 2025
View reviewed changes

Comment threadsrc/coreclr/jit/fgwasm.cpp Outdated

Fix more typos
890548e

AndyAyersMS requested a review from a teamNovember 7, 2025 15:31

AndyAyersMS mentioned this pull request Nov 7, 2025
[Wasm RyuJIT] Implement Wasm DFS and Loop Finding #121457
Merged

am11 added the arch-wasm WebAssembly architecture label Nov 7, 2025

Merge branch 'main' into WasmControlFlowBasics
9f9e0a6

This was referenced Nov 11, 2025
slow macOS - "##[error]The job running on agent Azure Pipelines 9 ran longer than the maximum time of 60 minutes." dotnet/dnceng#1883
Open
AppHost test failure: I/O failure when writing extracted files #120653
Closed

jakobbotsch self-requested a review November 11, 2025 18:24

SingleAccretion reviewed Nov 11, 2025
View reviewed changes

jakobbotsch reviewed Nov 11, 2025
View reviewed changes

Comment threadsrc/coreclr/jit/fgwasm.cpp

jakobbotsch reviewed Nov 11, 2025
View reviewed changes

Comment threadsrc/coreclr/jit/fgwasm.cpp

kg reviewed Nov 11, 2025
View reviewed changes

Comment threadsrc/coreclr/jit/fgwasm.cpp

jakobbotsch approved these changes Nov 12, 2025
View reviewed changes

AndyAyersMS added 3 commits November 13, 2025 13:09

Merge branch 'main' into WasmControlFlowBasics
4a7bf9e

review feedback
9094aeb

disable by default
c282fa1

AndyAyersMS merged commit b435b40 into dotnet:mainNov 14, 2025
109 of 112 checks passed

dotnet-maestroBot mentioned this pull request Nov 19, 2025
[main] Source code updates from dotnet/runtime dotnet/dotnet#3448
Merged

AndyAyersMS mentioned this pull request Nov 19, 2025
[Wasm RyuJIT] Basic Control Flow #121178
Closed
12 tasks

github-actionsBot locked and limited conversation to collaborators Dec 15, 2025

github-actionsBot added the area-CodeGen-coreclr CLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMI label Nov 6, 2025

dotnet-policy-serviceBot assigned AndyAyersMS Nov 6, 2025

fix release build
ca2c9b4

fix llvm build
39e0bd3

AndyAyersMS marked this pull request as ready for review November 6, 2025 23:48

CopilotAI review requested due to automatic review settings November 6, 2025 23:48

CopilotAI reviewed Nov 6, 2025
View reviewed changes

Comment threadsrc/coreclr/jit/fgwasm.cpp Outdated
Comment threadsrc/coreclr/jit/fgwasm.cpp Outdated
Comment threadsrc/coreclr/jit/fgwasm.cpp Outdated
Comment threadsrc/coreclr/jit/fgwasm.cpp Outdated
Comment threadsrc/coreclr/jit/fgwasm.cpp Outdated
Comment threadsrc/coreclr/jit/fgwasm.cpp Outdated

Fix typos
e8882ab
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

AndyAyersMS commented Nov 7, 2025
View reviewed changes

Comment threadsrc/coreclr/jit/fgwasm.cpp Outdated

Fix more typos
890548e

AndyAyersMS requested a review from a teamNovember 7, 2025 15:31

AndyAyersMS mentioned this pull request Nov 7, 2025
[Wasm RyuJIT] Implement Wasm DFS and Loop Finding #121457
Merged

am11 added the arch-wasm WebAssembly architecture label Nov 7, 2025

Merge branch 'main' into WasmControlFlowBasics
9f9e0a6

This was referenced Nov 11, 2025
slow macOS - "##[error]The job running on agent Azure Pipelines 9 ran longer than the maximum time of 60 minutes." dotnet/dnceng#1883
Open
AppHost test failure: I/O failure when writing extracted files #120653
Closed

jakobbotsch self-requested a review November 11, 2025 18:24

SingleAccretion reviewed Nov 11, 2025
View reviewed changes

jakobbotsch reviewed Nov 11, 2025
View reviewed changes

Comment threadsrc/coreclr/jit/fgwasm.cpp

jakobbotsch reviewed Nov 11, 2025
View reviewed changes

Comment threadsrc/coreclr/jit/fgwasm.cpp

kg reviewed Nov 11, 2025
View reviewed changes

Comment threadsrc/coreclr/jit/fgwasm.cpp

jakobbotsch approved these changes Nov 12, 2025
View reviewed changes

AndyAyersMS added 3 commits November 13, 2025 13:09

Merge branch 'main' into WasmControlFlowBasics
4a7bf9e

review feedback
9094aeb

disable by default
c282fa1

AndyAyersMS merged commit b435b40 into dotnet:mainNov 14, 2025
109 of 112 checks passed

dotnet-maestroBot mentioned this pull request Nov 19, 2025
[main] Source code updates from dotnet/runtime dotnet/dotnet#3448
Merged

AndyAyersMS mentioned this pull request Nov 19, 2025
[Wasm RyuJIT] Basic Control Flow #121178
Closed
12 tasks

github-actionsBot locked and limited conversation to collaborators Dec 15, 2025

github-actionsBot added the area-CodeGen-coreclr CLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMI label Nov 6, 2025

dotnet-policy-serviceBot assigned AndyAyersMS Nov 6, 2025

fix release build
ca2c9b4

fix llvm build
39e0bd3

AndyAyersMS marked this pull request as ready for review November 6, 2025 23:48

CopilotAI review requested due to automatic review settings November 6, 2025 23:48

CopilotAI reviewed Nov 6, 2025
View reviewed changes

Comment threadsrc/coreclr/jit/fgwasm.cpp Outdated
Comment threadsrc/coreclr/jit/fgwasm.cpp Outdated
Comment threadsrc/coreclr/jit/fgwasm.cpp Outdated
Comment threadsrc/coreclr/jit/fgwasm.cpp Outdated
Comment threadsrc/coreclr/jit/fgwasm.cpp Outdated
Comment threadsrc/coreclr/jit/fgwasm.cpp Outdated

Fix typos
e8882ab
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

AndyAyersMS commented Nov 7, 2025
View reviewed changes

Comment threadsrc/coreclr/jit/fgwasm.cpp Outdated

Fix more typos
890548e

AndyAyersMS requested a review from a teamNovember 7, 2025 15:31

AndyAyersMS mentioned this pull request Nov 7, 2025
[Wasm RyuJIT] Implement Wasm DFS and Loop Finding #121457
Merged

am11 added the arch-wasm WebAssembly architecture label Nov 7, 2025

Merge branch 'main' into WasmControlFlowBasics
9f9e0a6

This was referenced Nov 11, 2025
slow macOS - "##[error]The job running on agent Azure Pipelines 9 ran longer than the maximum time of 60 minutes." dotnet/dnceng#1883
Open
AppHost test failure: I/O failure when writing extracted files #120653
Closed

jakobbotsch self-requested a review November 11, 2025 18:24

SingleAccretion reviewed Nov 11, 2025
View reviewed changes

jakobbotsch reviewed Nov 11, 2025
View reviewed changes

Comment threadsrc/coreclr/jit/fgwasm.cpp

jakobbotsch reviewed Nov 11, 2025
View reviewed changes

Comment threadsrc/coreclr/jit/fgwasm.cpp

kg reviewed Nov 11, 2025
View reviewed changes

Comment threadsrc/coreclr/jit/fgwasm.cpp

jakobbotsch approved these changes Nov 12, 2025
View reviewed changes

AndyAyersMS added 3 commits November 13, 2025 13:09

Merge branch 'main' into WasmControlFlowBasics
4a7bf9e

review feedback
9094aeb

disable by default
c282fa1

AndyAyersMS merged commit b435b40 into dotnet:mainNov 14, 2025
109 of 112 checks passed

dotnet-maestroBot mentioned this pull request Nov 19, 2025
[main] Source code updates from dotnet/runtime dotnet/dotnet#3448
Merged

AndyAyersMS mentioned this pull request Nov 19, 2025
[Wasm RyuJIT] Basic Control Flow #121178
Closed
12 tasks

github-actionsBot locked and limited conversation to collaborators Dec 15, 2025

github-actionsBot added the area-CodeGen-coreclr CLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMI label Nov 6, 2025

dotnet-policy-serviceBot assigned AndyAyersMS Nov 6, 2025

fix release build
ca2c9b4

fix llvm build
39e0bd3

AndyAyersMS marked this pull request as ready for review November 6, 2025 23:48

CopilotAI review requested due to automatic review settings November 6, 2025 23:48

CopilotAI reviewed Nov 6, 2025
View reviewed changes

Comment threadsrc/coreclr/jit/fgwasm.cpp Outdated
Comment threadsrc/coreclr/jit/fgwasm.cpp Outdated
Comment threadsrc/coreclr/jit/fgwasm.cpp Outdated
Comment threadsrc/coreclr/jit/fgwasm.cpp Outdated
Comment threadsrc/coreclr/jit/fgwasm.cpp Outdated
Comment threadsrc/coreclr/jit/fgwasm.cpp Outdated

Fix typos
e8882ab
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

AndyAyersMS commented Nov 7, 2025
View reviewed changes

Comment threadsrc/coreclr/jit/fgwasm.cpp Outdated

Fix more typos
890548e

AndyAyersMS requested a review from a teamNovember 7, 2025 15:31

AndyAyersMS mentioned this pull request Nov 7, 2025
[Wasm RyuJIT] Implement Wasm DFS and Loop Finding #121457
Merged

am11 added the arch-wasm WebAssembly architecture label Nov 7, 2025

Merge branch 'main' into WasmControlFlowBasics
9f9e0a6

This was referenced Nov 11, 2025
slow macOS - "##[error]The job running on agent Azure Pipelines 9 ran longer than the maximum time of 60 minutes." dotnet/dnceng#1883
Open
AppHost test failure: I/O failure when writing extracted files #120653
Closed

jakobbotsch self-requested a review November 11, 2025 18:24

SingleAccretion reviewed Nov 11, 2025
View reviewed changes

jakobbotsch reviewed Nov 11, 2025
View reviewed changes

Comment threadsrc/coreclr/jit/fgwasm.cpp

jakobbotsch reviewed Nov 11, 2025
View reviewed changes

Comment threadsrc/coreclr/jit/fgwasm.cpp

kg reviewed Nov 11, 2025
View reviewed changes

Comment threadsrc/coreclr/jit/fgwasm.cpp

jakobbotsch approved these changes Nov 12, 2025
View reviewed changes

AndyAyersMS added 3 commits November 13, 2025 13:09

Merge branch 'main' into WasmControlFlowBasics
4a7bf9e

review feedback
9094aeb

disable by default
c282fa1

AndyAyersMS merged commit b435b40 into dotnet:mainNov 14, 2025
109 of 112 checks passed

dotnet-maestroBot mentioned this pull request Nov 19, 2025
[main] Source code updates from dotnet/runtime dotnet/dotnet#3448
Merged

AndyAyersMS mentioned this pull request Nov 19, 2025
[Wasm RyuJIT] Basic Control Flow #121178
Closed
12 tasks

github-actionsBot locked and limited conversation to collaborators Dec 15, 2025

github-actionsBot added the area-CodeGen-coreclr CLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMI label Nov 6, 2025

dotnet-policy-serviceBot assigned AndyAyersMS Nov 6, 2025

fix release build
ca2c9b4

fix llvm build
39e0bd3

AndyAyersMS marked this pull request as ready for review November 6, 2025 23:48

CopilotAI review requested due to automatic review settings November 6, 2025 23:48

CopilotAI reviewed Nov 6, 2025
View reviewed changes

Comment threadsrc/coreclr/jit/fgwasm.cpp Outdated
Comment threadsrc/coreclr/jit/fgwasm.cpp Outdated
Comment threadsrc/coreclr/jit/fgwasm.cpp Outdated
Comment threadsrc/coreclr/jit/fgwasm.cpp Outdated
Comment threadsrc/coreclr/jit/fgwasm.cpp Outdated
Comment threadsrc/coreclr/jit/fgwasm.cpp Outdated

Fix typos
e8882ab
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

AndyAyersMS commented Nov 7, 2025
View reviewed changes

Comment threadsrc/coreclr/jit/fgwasm.cpp Outdated

Fix more typos
890548e

AndyAyersMS requested a review from a teamNovember 7, 2025 15:31

AndyAyersMS mentioned this pull request Nov 7, 2025
[Wasm RyuJIT] Implement Wasm DFS and Loop Finding #121457
Merged

am11 added the arch-wasm WebAssembly architecture label Nov 7, 2025

Merge branch 'main' into WasmControlFlowBasics
9f9e0a6

This was referenced Nov 11, 2025
slow macOS - "##[error]The job running on agent Azure Pipelines 9 ran longer than the maximum time of 60 minutes." dotnet/dnceng#1883
Open
AppHost test failure: I/O failure when writing extracted files #120653
Closed

jakobbotsch self-requested a review November 11, 2025 18:24

SingleAccretion reviewed Nov 11, 2025
View reviewed changes

jakobbotsch reviewed Nov 11, 2025
View reviewed changes

Comment threadsrc/coreclr/jit/fgwasm.cpp

jakobbotsch reviewed Nov 11, 2025
View reviewed changes

Comment threadsrc/coreclr/jit/fgwasm.cpp

kg reviewed Nov 11, 2025
View reviewed changes

Comment threadsrc/coreclr/jit/fgwasm.cpp

jakobbotsch approved these changes Nov 12, 2025
View reviewed changes

AndyAyersMS added 3 commits November 13, 2025 13:09

Merge branch 'main' into WasmControlFlowBasics
4a7bf9e

review feedback
9094aeb

disable by default
c282fa1

AndyAyersMS merged commit b435b40 into dotnet:mainNov 14, 2025
109 of 112 checks passed

dotnet-maestroBot mentioned this pull request Nov 19, 2025
[main] Source code updates from dotnet/runtime dotnet/dotnet#3448
Merged

AndyAyersMS mentioned this pull request Nov 19, 2025
[Wasm RyuJIT] Basic Control Flow #121178
Closed
12 tasks

github-actionsBot locked and limited conversation to collaborators Dec 15, 2025

github-actionsBot added the area-CodeGen-coreclr CLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMI label Nov 6, 2025

dotnet-policy-serviceBot assigned AndyAyersMS Nov 6, 2025

fix release build
ca2c9b4

fix llvm build
39e0bd3

AndyAyersMS marked this pull request as ready for review November 6, 2025 23:48

CopilotAI review requested due to automatic review settings November 6, 2025 23:48

CopilotAI reviewed Nov 6, 2025
View reviewed changes

Comment threadsrc/coreclr/jit/fgwasm.cpp Outdated
Comment threadsrc/coreclr/jit/fgwasm.cpp Outdated
Comment threadsrc/coreclr/jit/fgwasm.cpp Outdated
Comment threadsrc/coreclr/jit/fgwasm.cpp Outdated
Comment threadsrc/coreclr/jit/fgwasm.cpp Outdated
Comment threadsrc/coreclr/jit/fgwasm.cpp Outdated

Fix typos
e8882ab
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

AndyAyersMS commented Nov 7, 2025
View reviewed changes

Comment threadsrc/coreclr/jit/fgwasm.cpp Outdated

Fix more typos
890548e

AndyAyersMS requested a review from a teamNovember 7, 2025 15:31

AndyAyersMS mentioned this pull request Nov 7, 2025
[Wasm RyuJIT] Implement Wasm DFS and Loop Finding #121457
Merged

am11 added the arch-wasm WebAssembly architecture label Nov 7, 2025

Merge branch 'main' into WasmControlFlowBasics
9f9e0a6

This was referenced Nov 11, 2025
slow macOS - "##[error]The job running on agent Azure Pipelines 9 ran longer than the maximum time of 60 minutes." dotnet/dnceng#1883
Open
AppHost test failure: I/O failure when writing extracted files #120653
Closed

jakobbotsch self-requested a review November 11, 2025 18:24

SingleAccretion reviewed Nov 11, 2025
View reviewed changes

jakobbotsch reviewed Nov 11, 2025
View reviewed changes

Comment threadsrc/coreclr/jit/fgwasm.cpp

jakobbotsch reviewed Nov 11, 2025
View reviewed changes

Comment threadsrc/coreclr/jit/fgwasm.cpp

kg reviewed Nov 11, 2025
View reviewed changes

Comment threadsrc/coreclr/jit/fgwasm.cpp

jakobbotsch approved these changes Nov 12, 2025
View reviewed changes

AndyAyersMS added 3 commits November 13, 2025 13:09

Merge branch 'main' into WasmControlFlowBasics
4a7bf9e

review feedback
9094aeb

disable by default
c282fa1

AndyAyersMS merged commit b435b40 into dotnet:mainNov 14, 2025
109 of 112 checks passed

dotnet-maestroBot mentioned this pull request Nov 19, 2025
[main] Source code updates from dotnet/runtime dotnet/dotnet#3448
Merged

AndyAyersMS mentioned this pull request Nov 19, 2025
[Wasm RyuJIT] Basic Control Flow #121178
Closed
12 tasks

github-actionsBot locked and limited conversation to collaborators Dec 15, 2025

github-actionsBot added the area-CodeGen-coreclr CLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMI label Nov 6, 2025

dotnet-policy-serviceBot assigned AndyAyersMS Nov 6, 2025

fix release build
ca2c9b4

fix llvm build
39e0bd3

AndyAyersMS marked this pull request as ready for review November 6, 2025 23:48

CopilotAI review requested due to automatic review settings November 6, 2025 23:48

CopilotAI reviewed Nov 6, 2025
View reviewed changes

Comment threadsrc/coreclr/jit/fgwasm.cpp Outdated
Comment threadsrc/coreclr/jit/fgwasm.cpp Outdated
Comment threadsrc/coreclr/jit/fgwasm.cpp Outdated
Comment threadsrc/coreclr/jit/fgwasm.cpp Outdated
Comment threadsrc/coreclr/jit/fgwasm.cpp Outdated
Comment threadsrc/coreclr/jit/fgwasm.cpp Outdated

Fix typos
e8882ab
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

AndyAyersMS commented Nov 7, 2025
View reviewed changes

Comment threadsrc/coreclr/jit/fgwasm.cpp Outdated

Fix more typos
890548e

AndyAyersMS requested a review from a teamNovember 7, 2025 15:31

AndyAyersMS mentioned this pull request Nov 7, 2025
[Wasm RyuJIT] Implement Wasm DFS and Loop Finding #121457
Merged

am11 added the arch-wasm WebAssembly architecture label Nov 7, 2025

Merge branch 'main' into WasmControlFlowBasics
9f9e0a6

This was referenced Nov 11, 2025
slow macOS - "##[error]The job running on agent Azure Pipelines 9 ran longer than the maximum time of 60 minutes." dotnet/dnceng#1883
Open
AppHost test failure: I/O failure when writing extracted files #120653
Closed

jakobbotsch self-requested a review November 11, 2025 18:24

SingleAccretion reviewed Nov 11, 2025
View reviewed changes

jakobbotsch reviewed Nov 11, 2025
View reviewed changes

Comment threadsrc/coreclr/jit/fgwasm.cpp

jakobbotsch reviewed Nov 11, 2025
View reviewed changes

Comment threadsrc/coreclr/jit/fgwasm.cpp

kg reviewed Nov 11, 2025
View reviewed changes

Comment threadsrc/coreclr/jit/fgwasm.cpp

jakobbotsch approved these changes Nov 12, 2025
View reviewed changes

AndyAyersMS added 3 commits November 13, 2025 13:09

Merge branch 'main' into WasmControlFlowBasics
4a7bf9e

review feedback
9094aeb

disable by default
c282fa1

AndyAyersMS merged commit b435b40 into dotnet:mainNov 14, 2025
109 of 112 checks passed

dotnet-maestroBot mentioned this pull request Nov 19, 2025
[main] Source code updates from dotnet/runtime dotnet/dotnet#3448
Merged

AndyAyersMS mentioned this pull request Nov 19, 2025
[Wasm RyuJIT] Basic Control Flow #121178
Closed
12 tasks

github-actionsBot locked and limited conversation to collaborators Dec 15, 2025

Uh oh!

Conversation

AndyAyersMS commented Nov 6, 2025

Uh oh!

AndyAyersMS commented Nov 6, 2025• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

AndyAyersMS commented Nov 6, 2025

Uh oh!

AndyAyersMS commented Nov 6, 2025

Uh oh!

CopilotAI left a comment

Choose a reason for hiding this comment

Pull Request Overview

Reviewed Changes

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

AndyAyersMS commented Nov 7, 2025

Uh oh!

dotnet-policy-serviceBot commented Nov 7, 2025

Uh oh!

AndyAyersMS commented Nov 10, 2025

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

kg commented Nov 11, 2025

Uh oh!

AndyAyersMS commented Nov 12, 2025

Uh oh!

AndyAyersMS commented Nov 13, 2025

Uh oh!

AndyAyersMS commented Nov 14, 2025

Uh oh!

AndyAyersMS commented Nov 14, 2025

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants

Uh oh!

Conversation

AndyAyersMS commented Nov 6, 2025

Uh oh!

AndyAyersMS commented Nov 6, 2025• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

AndyAyersMS commented Nov 6, 2025

Uh oh!

AndyAyersMS commented Nov 6, 2025

Uh oh!

CopilotAI left a comment

Choose a reason for hiding this comment

Pull Request Overview

Reviewed Changes

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

AndyAyersMS commented Nov 6, 2025•
edited
Loading

AndyAyersMS commented Nov 6, 2025•
edited
Loading

AndyAyersMS commented Nov 6, 2025•
edited
Loading