-
Notifications
You must be signed in to change notification settings - Fork 722
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix bug in resolution of VT arrays and fields #8646
Merged
Merged
Conversation
This file contains 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
tajila
force-pushed
the
vt3
branch
5 times, most recently
from
February 24, 2020 23:14
7612a25
to
23aaf53
Compare
@gacholio please review these changes |
tajila
force-pushed
the
vt3
branch
2 times, most recently
from
February 25, 2020 14:49
1206e1d
to
ebc83d1
Compare
gacholio
reviewed
Feb 25, 2020
Why is this necessary? |
Could you make your commit message more descriptive in what the problem is you're fixing please? |
tajila
force-pushed
the
vt3
branch
7 times, most recently
from
February 25, 2020 17:21
4a78a69
to
1035304
Compare
gacholio
reviewed
Feb 25, 2020
gacholio
reviewed
Feb 26, 2020
When creating an array the elements of the array are set to the default value. For arrays of regular identity types this is NULL. For arrays of valueTypes this is the defaultValue of the valueType. As a result, if the element type of the array is a valueType, the element type must be fully initialized before the array can be created. This PR addresses this problem. Also, in the resolve field code, it is incorrectly fetching the flattened field cache from the class where the fieldref is stored instead of the class that defined the field. We havent noticed this because the existing tests only fetches fields using getter methods. Signed-off-by: Tobi Ajila <atobia@ca.ibm.com>
gacholio
approved these changes
Feb 26, 2020
jenkins test sanity xlinux jdk8 |
1 similar comment
jenkins test sanity xlinux jdk8 |
Test failures are:
|
Enough has run to convince me. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fix bug in resolution of VT arrays and fields
When creating an array the elements of the array are set to the default
value. For arrays of regular identity types this is NULL. For arrays of
valueTypes this is the defaultValue of the valueType. As a result, if
the element type of the array is a valueType, the element type must be
fully initialized before the array can be created. This PR addresses
this problem.
Also, in the resolve field code, it is incorrectly fetching the
flattened field cache from the class where the fieldref is stored
instead of the class that defined the field. We havent noticed this
because the existing tests only fetches fields using getter methods.
Signed-off-by: Tobi Ajila atobia@ca.ibm.com