SPMI collections need to use release System.Private.Corelib

[AndyAyersMS]

Checked builds of SPC contain Debug.Assert and other constructs that can give a misleading picture of codegen diffs.

See eg: #60943 (comment)

category:eng-sys
theme:super-pmi
skill-level:intermediate
cost:medium
impact:medium

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

Issue Details

---

Checked builds of SPC contain Debug.Assert and other constructs that can give a misleading picture of codegen diffs.

See eg: #60943 (comment)

Author:	AndyAyersMS
Assignees:	-
Labels:	area-CodeGen-coreclr, untriaged
Milestone:	-

[AndyAyersMS]

cc @dotnet/jit-contrib

[BruceForstall]

Currently, SPMI collections use Checked builds for everything. Should we use Release builds with an overlaid Checked JIT? I believe we need the Checked JIT, which will ask additional questions (mostly to get the full function names for Checked/Debug playback with JitDump).

Needing more than just Checked builds complicates things.

[AndyAyersMS]

Should we use Release builds with an overlaid Checked JIT?

Yes, that's what I'd recommend. jit-diffs --pmi was intentionally set up this way.