Fix JITEEInterface::IsValueClass to return false for pointers.#50749
Merged
Conversation
Contributor
Author
|
PTAL @jkotas, @AndyAyersMS , cc @MichalStrehovsky @dotnet/jit-contrib |
sandreenko
marked this pull request as ready for review
April 6, 2021 02:09
Contributor
Author
|
There are no diffs crossgen/pmi on --f. I have manually collected dasm for base and diff using different VM versions and checked with jit-analyze. |
Member
|
Could you please also make a matching change in Change And delete this from The VM side of the change looks good to me otherwise. |
sandreenko
force-pushed
the
FixisValueClass
branch
from
April 11, 2021 20:55
46c37bc to
e1d07cf
Compare
Contributor
Author
|
ping @dotnet/jit-contrib |
AndyAyersMS
reviewed
Apr 12, 2021
AndyAyersMS
left a comment
Member
There was a problem hiding this comment.
This will need a new jit GUID.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Fixes #44730
In the past, we did not see REF types from
ldobj handle, we had:and jit treated it like a value type with POINTER_SIZE(in this case 8-byte, so used long):
after the VM change we see the real REF type (a pointer to an object on a heap):
Note that we allow REF->IMPL conversion, but not IMPL->REF, cc @AndyAyersMS .
I guess I need to revert part of #44465 but not sure what exactly.