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
8265606: Reduce allocations in AdapterHandlerLibrary::get_adapter #3595
Conversation
👋 Welcome back redestad! A progress list of the required criteria for merging this PR into |
Webrevs
|
/label remove hotspot |
@cl4es |
@cl4es |
@@ -2954,7 +2961,7 @@ VMRegPair *SharedRuntime::find_callee_arguments(Symbol* sig, bool has_receiver, | |||
// This method is returning a data structure allocating as a | |||
// ResourceObject, so do not put any ResourceMarks in here. | |||
|
|||
BasicType *sig_bt = NEW_RESOURCE_ARRAY(BasicType, 256); | |||
BasicType sig_bt[256]; |
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.
Was this line changed by mistake? The rest of the PR looks good to me.
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.
It was intentional, but it's also a bit of a scope creep: this method is about creating and returning the VMRegPair array, but it also resource-allocs this sig_bt array and keeps it alive for however long the regs array is kept alive, which means we hold on to a bit more memory for longer for no reason.
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.
The think the original code was written to avoid allocating large arrays on the stack.
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.
Ok, I reverted this change. It's not part of anything I know sees much use anyhow.
@cl4es 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 43 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 |
/integrate |
@cl4es Since your change was applied there have been 77 commits pushed to the
Your commit was automatically rebased without conflicts. Pushed as commit 891f72f. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Use stack allocated arrays used when looking up and creating adapters. Resource allocate if number of args grows large, which is relatively rare.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/3595/head:pull/3595
$ git checkout pull/3595
Update a local copy of the PR:
$ git checkout pull/3595
$ git pull https://git.openjdk.java.net/jdk pull/3595/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 3595
View PR using the GUI difftool:
$ git pr show -t 3595
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/3595.diff