JIT: remove incorrect type deduction for an Unsafe.As case #93694
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.
Thanks to @SingleAccretion for the fix.
The JIT was assuming that an indirectly accessed value type field had the type of the field, but that might not be the case if the field was accessed via
Unsafe.As
.Fix this by limiting type deduction from these indirectly accessed fields to only ref type fields.
Closes #93650.