-
Notifications
You must be signed in to change notification settings - Fork 6.2k
8321515: ARM32: Move method resolution information out of the cpCache properly #17017
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
|
👋 Welcome back avoitylov! A progress list of the required criteria for merging this PR into |
Webrevs
|
|
Thanks for fixing the ARM32 build! |
|
thanks @bulasevich. Any Reviewers, please? I'd like to to get the ARM32 port to work again. |
shipilev
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 okay, but I have suggestions.
| ldr(cache, Address(cache, ConstantPoolCache::method_entries_offset())); | ||
| add(cache, cache, Array<ResolvedMethodEntry>::base_offset_in_bytes()); | ||
| add(cache, cache, index); | ||
| if (is_power_of_2(sizeof(ResolvedMethodEntry))) { |
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.
I usually dislike introducing split like these, because one of the branches is effectively dead. Which also means it is effectively untested. Given this interpreter code, can we just leave the generic version unconditionally?
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.
Yes, it's gone in the new version.
| } | ||
| else { |
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.
| } | |
| else { | |
| } else { |
|
Also changed target-version to 23 in JBS, so that we don't create the backports when we push. You might want to pull and merge the new master to get new mainline with jcheck config for 23. |
|
@voitylov 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 12 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. As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@shipilev) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
shipilev
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.
Still good.
|
Thanks for this fix @voitylov! |
|
/integrate |
|
Thanks again Boris, Matias and Aleksey! |
|
/sponsor |
|
Going to push as commit f573f6d.
Your commit was automatically rebased without conflicts. |
|
/backport jdk22 |
|
@voitylov the backport was successfully created on the branch backport-voitylov-f573f6d2 in my personal fork of openjdk/jdk22. To create a pull request with this backport targeting openjdk/jdk22:master, just click the following link: The title of the pull request is automatically filled in correctly and below you find a suggestion for the pull request body:
If you need to update the source branch of the pull then run the following commands in a local clone of your personal fork of openjdk/jdk22: |
Thanks to @matias9927, JDK-8320278 fixed the JDK build for ARM32 after JDK-8301997. This PR introduces some additional fixes that enable the ARM32 port to actually work.
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/17017/head:pull/17017$ git checkout pull/17017Update a local copy of the PR:
$ git checkout pull/17017$ git pull https://git.openjdk.org/jdk.git pull/17017/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 17017View PR using the GUI difftool:
$ git pr show -t 17017Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/17017.diff
Webrev
Link to Webrev Comment