[browser][coreCLR] Support interpreter code resolution on portable entrypoint platforms

[pavelsavara]

Summary

Generalizes GetInterpreterCodeFromInterpreterPrecodeIfPresent (renamed to GetInterpreterCodeFromEntryPointIfPresent) to resolve interpreter bytecode addresses on platforms that use FEATURE_PORTABLE_ENTRYPOINTS (e.g., browser WASM) where InterpreterPrecode does not exist.

Motivation

The sampling profiler does not work on WASM because the EventPipe code paths that resolve instruction pointers (IPs) to method information assume the traditional InterpreterPrecode mechanism. On WASM, CoreCLR uses portable entrypoints (FEATURE_PORTABLE_ENTRYPOINTS) instead of interpreter precodes, so the existing code silently returns wrong or zero addresses, causing the profiler to fail to attribute samples to managed methods.

Split from #126324 for smaller reviews

Changes

Renamed function with new signature

• GetInterpreterCodeFromInterpreterPrecodeIfPresent(TADDR) → GetInterpreterCodeFromEntryPointIfPresent(TADDR, MethodDesc*)
• The new pMethodDesc parameter (defaulting to NULL) enables resolution on portable entrypoint platforms via MethodDesc::GetInterpreterCode().

New portable entrypoint code path (precode.cpp)

Added #elif defined(FEATURE_INTERPRETER) && defined(FEATURE_PORTABLE_ENTRYPOINTS) branch:

• When pMethodDesc is provided, calls pMethodDesc->GetInterpreterCode() to get the InterpByteCodeStart pointer directly from the MethodDesc, bypassing the precode entirely.
• Falls through to returning the original entry point when pMethodDesc is NULL or no interpreter code exists.

Portable entrypoint handling in prestub.cpp

Added #ifdef FEATURE_PORTABLE_ENTRYPOINTS branch in JitCompileCodeLockedEventWrapper to use PortableEntryPoint::GetInterpreterData(pCode) instead of InterpreterPrecode::FromEntryPoint(pCode) when extracting the InterpByteCodeStart for ETW method-jitted events.

Caller updates (DAC/debugger/ETW)

All callers updated to pass the new MethodDesc* parameter where available:

• daccess.cpp — GetMethodVarInfo, GetMethodNativeMap, RawGetMethodName
• dacdbiimpl.cpp — GetNativeCodeInfoForAddr
• request.cpp — CopyNativeCodeVersionToReJitData, GetMethodDescData, GetTieredVersions
• functioninfo.cpp — CreateDJIsForMethodDesc
• eventtrace.cpp — MethodAndStartAddressToEECodeInfoPointer (passes NULL when a specific code address was provided, pMethodDesc otherwise)
• method.hpp — GetCodeForInterpreterOrJitted

[dotnet-policy-service]

Tagging subscribers to this area: @steveisok, @tommcdon, @dotnet/dotnet-diag
See info in area-owners.md if you want to be subscribed.

[Copilot]

Pull request overview

This PR fixes EventPipe/ETW instruction-pointer (IP) to managed-method resolution for interpreted methods on WASM, where CoreCLR uses FEATURE_PORTABLE_ENTRYPOINTS instead of interpreter precodes. This enables the sampling profiler to correctly attribute samples to interpreted managed methods.

Changes:

• Update MethodDesc::JitCompileCodeLockedEventWrapper to derive the interpreted-method “native start address” from PortableEntryPoint interpreter data when FEATURE_PORTABLE_ENTRYPOINTS is enabled.
• Update MethodAndStartAddressToEECodeInfoPointer to fall back to MethodDesc::GetInterpreterCode() (returning the InterpByteCodeStart pointer) when no explicit start address is supplied on portable-entrypoint interpreter builds.

Reviewed changes

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

File	Description
src/coreclr/vm/prestub.cpp	Uses PortableEntryPoint::GetInterpreterData to compute the method start address for interpreted-method ETW events under portable entrypoints.
src/coreclr/vm/eventtrace.cpp	Adds a portable-entrypoints interpreter fallback so method events can resolve InterpByteCodeStart when no explicit start address is provided.

[Copilot]

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

[Copilot]

Pull request overview

Copilot reviewed 9 out of 9 changed files in this pull request and generated 1 comment.