[browser][CoreCLR] Resolve ReadyToRun addresses for EventPipe

[lewing]

Summary

Fix EventPipe method load, rundown, and IL-to-native-map resolution for ReadyToRun methods on CoreCLR browser-Wasm.

On TARGET_WASM with FEATURE_PORTABLE_ENTRYPOINTS, ReadyToRunInfo::GetEntryPoint publishes a callable PortableEntryPoint whose actual code is a global Wasm function-table index. The corresponding MethodDesc and ReadyToRunJitManager range are registered under a synthetic virtual IP. EventPipe previously passed the portable-entrypoint address to EECodeInfo, which could not resolve it through ExecutionManager; the existing EECodeInfo::IsValid guard then omitted the R2R method event.

MethodAndStartAddressToEECodeInfoPointer now preserves interpreter resolution first, then translates a native Wasm portable entrypoint's function-table index through ExecutionManager::GetWasmVirtualIPFromFunctionTableIndex. Keeping the conversion in the shared EventPipe helper covers both method events and IL-to-native-map events. The existing mapping also preserves controlling-method behavior for funclet indices.

Non-Wasm behavior, explicit JIT code addresses, interpreter bytecode addresses, generic method handling, and the EECodeInfo::IsValid defense remain unchanged.

The browser CPU-sampling test is re-enabled for CoreCLR and now verifies both:

• the sampled application frame for Counter.IncrementCount; and
• on CoreCLR, rundown resolution for the ReadyToRun System.Buffer.Memmove framework method.

Validation

• ./build.sh clr+libs+host
• ./build.sh clr
• PATH="/opt/homebrew/bin:$PATH" ./build.sh -os browser -arch wasm -c Release -subset clr+libs -cmakeargs "-DCMAKE_CXX_FLAGS=-Wno-error=unguarded-availability-new"
  • The warning suppression is limited to an unrelated Xcode pipe2 availability diagnostic in the host-side universal-Wasm JIT build.
• Wasm.Build.Tests.Blazor.EventPipeDiagnosticsTests on CoreCLR browser-Wasm, workload lane: 4 passed, 0 failed, 0 skipped (metrics, heap dump, and CPU samples in Debug and Release).

A mutation attempt that removed only the address conversion could not provide trustworthy red evidence because the local workload installation cached a runtime pack with the same package version. The final fixed browser runtime and strengthened end-to-end tests were rebuilt and rerun successfully.

Resolves #132410

Note

This pull request description was generated with the assistance of GitHub Copilot.

[azure-pipelines]

Azure Pipelines:
Successfully started running 3 pipeline(s).
13 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

[dotnet-policy-service]

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

[Copilot]

Copilot review overview

🟡 Changes recommended

Fix the EventPipe contract boundary and guard the ReadyToRun assertion for CoreCLR-only runs.

Get a fresh assessment by requesting another Copilot review.

Review tier: Lite
Findings: 1

Open (1)

• Gate the ReadyToRun assertion to CoreCLR · New

What changed in this PR

Fixes WASM EventPipe ReadyToRun address and symbol resolution.

Changes:

• Maps R2R function-table indices to synthetic virtual IPs.
• Extends diagnostics coverage for System.Buffer.Memmove.
• Removes the prior CoreCLR issue suppression.

File	Summary
src/​mono/​wasm/​Wasm.Build.Tests/​Blazor/​EventPipeDiagnosticsTests.cs	Adds ReadyToRun symbol validation.
src/​coreclr/​vm/​eventtrace.cpp	Resolves WASM R2R entry points for EventPipe.

[Copilot]

Copilot review overview

🟢 Approval recommended

No unresolved blocking issues were identified.

Review tier: Lite
Findings: None

Resolved since last review (1)

• Gate the ReadyToRun assertion to CoreCLR