-
Notifications
You must be signed in to change notification settings - Fork 6.2k
8284760: Correct type/array element offset in LibraryCallKit::get_state_from_digest_object() #8208
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
Conversation
…te_from_digest_object()
|
👋 Welcome back rkennke! A progress list of the required criteria for merging this PR into |
rwestrel
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks reasonable to me.
|
@rkennke This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be: You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 21 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details. ➡️ To integrate this PR with the above commit message to the |
vnkozlov
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. Let me test it before approval.
vnkozlov
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Testing passed.
Thank you, Vladimir! /integrate |
|
Going to push as commit 2ba5cc4.
Your commit was automatically rebased without conflicts. |
In LibraryCallKit::get_state_from_digest_object() we call array_element_address() with T_INT, even though the input array might also be T_BYTE or T_LONG. This doesn't currently matter much: array elements always start at the same offset regardless of the element type. In Lilliput I'm trying to tighten the start of array elements though, and this causes problems because I can do smaller alignments for T_BYTE and T_INT, but not for T_LONG.
See also: openjdk/lilliput#41
Let's just use the correct type in array_element_address().
Testing:
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/8208/head:pull/8208$ git checkout pull/8208Update a local copy of the PR:
$ git checkout pull/8208$ git pull https://git.openjdk.java.net/jdk pull/8208/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 8208View PR using the GUI difftool:
$ git pr show -t 8208Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/8208.diff