JIT: Use fgCalledCount in inlinee weight computation

[amanasifkhalid]

I noticed that tweaking the computation of the entry weight for OSR methods (in service of #111915) incurred large inlining diffs. This is due to the fact that we use the entry block's weight to compute the normalized weight of a call site. This means we will get the wrong normalized weight for call sites when the entry block's weight diverges from the method's call count. This is currently possible only when the entry block is part of a loop, or when we compute a weight for the OSR entry fixup block that differs from fgCalledCount (which we almost always do). The correct thing to do is to use the root method's call count to normalize the call site's weight.

[Copilot]

Copilot wasn't able to review any files in this pull request.

Files not reviewed (1)

• src/coreclr/jit/importer.cpp: Language not supported

[dotnet-policy-service]

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

[amanasifkhalid]

@dotnet/jit-contrib PTAL. Diffs seem to be only in OSR methods. In the cases where we're now doing less inlining, the OSR loop's execution count is less than 100x the method call count; the opposite is true for cases where we're doing more inlining. With this change, we're doing fewer inlines overall. Thanks!

[amanasifkhalid]

@AndyAyersMS could you PTAL? Thanks!

[amanasifkhalid]

ping @AndyAyersMS