-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
8295012: Arena should not derive from CHeapObj<mtNone> #10621
Conversation
👋 Welcome back kbarrett! A progress list of the required criteria for merging this PR into |
@kimbarrett 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. |
Webrevs
|
src/hotspot/share/memory/arena.hpp
Outdated
@@ -86,7 +86,7 @@ class Chunk: CHeapObj<mtChunk> { | |||
|
|||
//------------------------------Arena------------------------------------------ | |||
// Fast allocation of memory | |||
class Arena : public CHeapObj<mtNone> { | |||
class Arena { |
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 allocation base class tells the reader that Arena
has special allocation constraints, by removing this it is not apparent there are any such constraints. Can we at least add a comment?
I confess I've forgotten how not having an allocation base class prevents use of new Foo()
??
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.
We have a link-time check in debug builds that fails the build if someone tries to use the global new operators.
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's the reason for keeping the new/delete operators in Arena, instead of inheriting from the newly introduced CHeapObjBase class?
No good reason. I just forgot about them. I will make that change. |
@kimbarrett 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 1 new commit pushed to the
Please see this link for an up-to-date comparison between the source branch of this pull request and the ➡️ To integrate this PR with the above commit message to the |
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!
Thanks
Thanks @stefank and @dholmes-ora for reviews. |
/integrate |
@kimbarrett Pushed as commit 5ad126f. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Please review this change to the
Arena
class. Rather than deriving fromCHeapObj<mtNone>
(which has the effect of preventing C-heap allocation for anarena by asserting if such is attempted), instead have no allocation base
class so that
new Arena(...)
will fail to compile.Testing: mach5 tier1
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk pull/10621/head:pull/10621
$ git checkout pull/10621
Update a local copy of the PR:
$ git checkout pull/10621
$ git pull https://git.openjdk.org/jdk pull/10621/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 10621
View PR using the GUI difftool:
$ git pr show -t 10621
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/10621.diff