-
Notifications
You must be signed in to change notification settings - Fork 218
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
8280872: Reorder code cache segments to improve code density #743
Conversation
👋 Welcome back eastigeevich! A progress list of the required criteria for merging this PR into |
This backport pull request has now been updated with issue from the original commit. |
@eastig 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 51 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. ➡️ To flag this PR as ready for integration with the above commit message, type |
/integrate |
/sponsor |
Going to push as commit d4d2e34.
Your commit was automatically rebased without conflicts. |
@phohensee @eastig Pushed as commit d4d2e34. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
A backport of reordering code cache segments from
[non-nmethod, non-profiled, profiled]
to
[profiled, non-nmethod, non-profiled]
AArch64 limits branch ranges to 128MB. Far jumps uses three instructions.
With the new order the aarch64 backend does not need far jumps to non-nmethods
for CodeCache sizes from 128M to 240MB.
The risk of changes is low. It only causes generated code reduction.
Tested with fastdebug and release builds:
Progress
Issue
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk17u-dev pull/743/head:pull/743
$ git checkout pull/743
Update a local copy of the PR:
$ git checkout pull/743
$ git pull https://git.openjdk.org/jdk17u-dev pull/743/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 743
View PR using the GUI difftool:
$ git pr show -t 743
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk17u-dev/pull/743.diff