-
Notifications
You must be signed in to change notification settings - Fork 5.8k
8255298: Remove SurvivorAlignmentInBytes functionality #838
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
8255298: Remove SurvivorAlignmentInBytes functionality #838
Conversation
👋 Welcome back tschatzl! A progress list of the required criteria for merging this PR into |
Webrevs
|
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.
Nifty cleanup! One nit I see:
@@ -32,7 +32,7 @@ | |||
HeapWord* PSYoungPromotionLAB::allocate(size_t size) { | |||
// Can't assert this, when young fills, we keep the LAB around, but flushed. | |||
// assert(_state != flushed, "Sanity"); | |||
HeapWord* obj = CollectedHeap::align_allocation_or_fail(top(), end(), SurvivorAlignmentInBytes); | |||
HeapWord* obj = top(); | |||
if (obj == NULL) { |
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.
obj
cannot be NULL
now? Thus the following null-check is redundant?
Done, thanks for catching this. |
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.
These look fine to me.
@tschatzl 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 64 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 |
HeapWord* new_top = obj + size; | ||
// The 'new_top>obj' check is needed to detect overflow of obj+size. | ||
if (new_top > obj && new_top <= end()) { | ||
set_top(new_top); | ||
assert(is_aligned(obj, SurvivorAlignmentInBytes) && is_object_aligned(new_top), | ||
"checking alignment"); | ||
assert(is_object_aligned(new_top), "checking alignment"); | ||
return obj; | ||
} else { | ||
set_top(obj); |
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.
I think we don't need this set_top anymore.
@kimbarrett : fixed in new revision. Thanks! |
Thanks @kstefanj @kimbarrett @shipilev for your reviews. /integrate |
@tschatzl Since your change was applied there have been 89 commits pushed to the
Your commit was automatically rebased without conflicts. Pushed as commit 38574d5. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Hi all,
can I have reviews to remove the SurvivorAlignmentInBytes functionality? It has not been in use for a long time if ever, and can be removed. Searching the web also indicates that apart from the usual lists of all options and CRs it is never mentioned.
SurvivorAlignmentInBytes is an experimental option so no further process is required.
Testing: tier1-5
Thanks,
Thomas
Progress
Issue
Reviewers
Download
$ git fetch https://git.openjdk.java.net/jdk pull/838/head:pull/838
$ git checkout pull/838