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
8277824: Remove empty RefProcSubPhasesWorkerTimeTracker destructor #6555
Conversation
|
@albertnetymk 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
|
@albertnetymk This change now passes all automated pre-integration checks. 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 39 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.
|
protected: | ||
WorkerDataArray<double>* _worker_time; | ||
double _start_time; | ||
uint _worker_id; | ||
public: | ||
RefProcWorkerTimeTracker(WorkerDataArray<double>* worker_time, uint worker_id); | ||
virtual ~RefProcWorkerTimeTracker(); | ||
~RefProcWorkerTimeTracker(); |
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 usual guideline is that the destructor for a baseclass should be either
public and virtual or protected and non-virtual. This prevents destructor
slicing by delete
. That the base class in question is a StackObj mitigates
against that kind of error.
And indeed, if I recall correctly, because it's now a StackObj its destructor
can't be virtual, because that would run afoul of the induced "deleting
destructor".
There are some relevant warning options that I occasionally look at and
remember why I think they aren't right for us, so we can't ever enable them
(-Wdelete-non-virtual-dtor and -Wnon-virtual-dtor).
But all that is kind of irrelevant. The real design problem here is that
RefProcSubPhasesWorkerTimeTracker is derived from RefProcWorkerTimeTracker.
It should instead have a RefProceWorkerTimeTracker. That would eliminate
all the discussion about base class destructors, and would also make
RefProcWorkerTimeTracker no longer need to perform double-duty as both a base
class and as a concrete class (which is often problematic).
Switched to composition from inheritance as suggested. /contributor add kbarrett |
@albertnetymk |
Thanks for the review. /integrate |
Going to push as commit fde6fe7.
Your commit was automatically rebased without conflicts. |
@albertnetymk Pushed as commit fde6fe7. |
Simple change removing effectively dead code, and some general cleanup.
Test: hotspot_gc
Progress
Issue
Reviewers
Contributors
<kbarrett@openjdk.org>
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/6555/head:pull/6555
$ git checkout pull/6555
Update a local copy of the PR:
$ git checkout pull/6555
$ git pull https://git.openjdk.java.net/jdk pull/6555/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 6555
View PR using the GUI difftool:
$ git pr show -t 6555
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/6555.diff