-
Notifications
You must be signed in to change notification settings - Fork 6.1k
8349580: Do not use address in MemTracker top level functions #23497
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 jsjolen! A progress list of the required criteria for merging this PR into |
|
@jdksjolen 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 52 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 |
|
@jdksjolen The following label will be automatically applied to this pull request:
When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command. |
| assert_post_init(); | ||
| if (!enabled()) return; | ||
| if (addr != nullptr) { | ||
| VirtualMemoryTracker::remove_released_region((address)addr, size); |
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.
What about here?
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.
Hi,
That's correct as VMT does take address, whilst the external API takes "regular" pointers.
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.
Hmm, looks weird. Are we planning on cleaning this up further up the chain then?
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.
That is not the plan, no. I believe that the address typedef is there to signify that we are concerned with storing addresses, but not dereferencing them.
gerard-ziemski
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.
LGTM
|
/integrate |
|
Going to push as commit f74c4df.
Your commit was automatically rebased without conflicts. |
|
@jdksjolen Pushed as commit f74c4df. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
|
We use |
Hi,
Please consider this trivial patch. Note that this gives us consistency with
reserve_memory.Thanks.
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/23497/head:pull/23497$ git checkout pull/23497Update a local copy of the PR:
$ git checkout pull/23497$ git pull https://git.openjdk.org/jdk.git pull/23497/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 23497View PR using the GUI difftool:
$ git pr show -t 23497Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/23497.diff
Using Webrev
Link to Webrev Comment