[release/8.0] JIT: remove incorrect type deduction for an Unsafe.As case #93703
+53
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Backport of #93694 to release/8.0
/cc @AndyAyersMS
Customer Impact
Regression from prior releases, reported by @pentp in #93650.
In some uncommon cases using
Unsafe.As
on a reference to a value class struct field, the JIT may use the type of the field as the type, instead of the cast-to type.Testing
Verified repro case is now fixed, no diffs in SPMI.
Risk
Low. This is a fairly surgical fix and makes the JIT more conservative.