JIT: Enable profile consistency checking up to morph

[amanasifkhalid]

Part of #107749. Stopping before morph seems like a sensible place, since maintaining the profile through morph will keep throw blocks with flow into them hot -- I expect that will incur plenty of diffs.

Waiting for #111006 and #111009 to go through first.

[dotnet-policy-service]

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

[amanasifkhalid]

/azp run runtime-coreclr outerloop, Fuzzlyn, Antigen

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[amanasifkhalid]

/azp run runtime-coreclr outerloop, Fuzzlyn, Antigen

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[amanasifkhalid]

cc @dotnet/jit-contrib, @AndyAyersMS PTAL. Fuzzers didn't find any profile-related issues, and the outerloop runs are hitting #110958. Diffs are limited since we're missing some collections, though they're still fairly dramatic -- I suspect most of this churn is from tail-merging based on the diffs from #110656, and from the tweaks to fgFoldConditional since that's called in various phases. Diffs look to be largely in layout and LSRA.

[AndyAyersMS]

Thanks!

Would be interested in seeing stats on how many methods are consistent through morph.

[amanasifkhalid]

Would be interested in seeing stats on how many methods are consistent through morph.

Yeah, I plan on adding metrics in the next push. After morph seems like a good place to run profile repair, since that's where we currently try to fill in the blanks with fgComputeBlockWeights, optSetBlockWeights, etc.