-
Notifications
You must be signed in to change notification settings - Fork 6.2k
8367972: ZGC: Reduce ZBarrierSet includes #27386
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
base: master
Are you sure you want to change the base?
Conversation
👋 Welcome back aboldtch! A progress list of the required criteria for merging this PR into |
@xmas92 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 29 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 |
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.
Looks good if the performance evaluation looks good.
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.
Looks good.
Hi @xmas92, some more data about this change. Before
After
|
JDK-8365053 made a fact which is already well known to ZGC developers clear. We pull in large parts of the ZGC implementation through the access API, via
zbarrierset.inline.hpp
.ZGC developers are well aware as touching most
.hpp
orinline.hpp
files ingc/z
requires rebuilding most of hotspot in incremental builds.I propose we create a boundary between the barrier set and the implementation. The main reason being making incremental builds less painful.
I experimented with this last year, at the time I saw no real difference in full build times, nor any performance regressions from not inlining the barrier implementation into the access API.
Will reevaluate the performance implications.
I ran the
bin/update_pch.sh
script, but with the defaultMIN_MS
I saw the same list both before and after this change:However when running with
MIN_MS
reduced by an order of magnitude#include "gc/z/zBarrier.inline.hpp"
was included without this patch, and was excluded after with this patch.Also cross-compiled ppc64le, s390x and riscv64 (fast debug). Could not find any missing includes, have not built all configurations.
For some reason windows slow debug failed to build because
test/hotspot/gtest/runtime/test_os_windows.cpp
was missingos_windows.hpp
, did not investigate further, but includedruntime/os.inline.hpp
in the test as it includes all OS and OS CPU specific declarations and inline definitions.Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/27386/head:pull/27386
$ git checkout pull/27386
Update a local copy of the PR:
$ git checkout pull/27386
$ git pull https://git.openjdk.org/jdk.git pull/27386/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 27386
View PR using the GUI difftool:
$ git pr show -t 27386
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/27386.diff
Using Webrev
Link to Webrev Comment