-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
8290706: Remove the support for inline contiguous allocations #9576
8290706: Remove the support for inline contiguous allocations #9576
Conversation
👋 Welcome back shade! A progress list of the required criteria for merging this PR into |
jtreg:test/hotspot/jtreg:tier1 succeeded (without gtests) on ppc64le. More tests overnight. |
:hotspot and :tier1 is OK on ARM32 |
Performed tier1 test on riscv64-linux. Result looks good. |
Got assert on arm-server-fastdebug. (Update) master seems affected as well. So this is an unrelated issue.
|
All right, so the current status is that all platforms (except for S390X test) are checked. GHA are also happy. Please do formal reviews :) |
I do not see a particular risk for s390x, mainly because the path being removed was never implemented for s390x. |
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 in general. However, the StorePConditionalNode is dead after this change, and I think we should remove that one as well while we are at it. AFAIK it is only used for the atomic bump pointer code. There is a whole bunch of StorePConditional matching rules in all the ad files that can be nuked, and a few mentions of Op_StorePConditional in C2 that can be removed.
True. I'd rather do that after this change lands, as to not invalidate the platform testing already done here. It would be also beneficial for potential bisects to have two atomic commits -- one removing the code from allocation paths, and another removing the C2 nodes and match rules. WDYT? |
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.
Good. It's nice to get rid of that code.
Yes, I agree. There's more cruft in there. |
@shipilev 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 33 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.
No findings in our CI testing which includes JCK and JTREG tests on the standard platforms and also on Linux/PPC64le.
I've reviewed the ppc changes. They look good to me.
Thanks, Richard.
Sounds good to me. |
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.
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.
RISCV-specific changes looks good to me. Thanks.
All right, thank you all, I will be integrating soon then. @TobiHartmann, @vnkozlov -- want to sanity check the C2 refactor? |
FYI, that would hopefully be in #9636 -- we can remove quite a bit more than just |
Let me will look into it. JDK-8291003 |
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.
JIT changes look good to me.
All right, thank you all. I am integrating and dealing with the rest of the issues, if any, later. /integrate |
Going to push as commit 8159a1a.
Your commit was automatically rebased without conflicts. |
See the bug for rationale and link to RFC.
This removes the 3rd allocation path (first two being TLAB and native GC interface), that is used by Serial/Parallel when TLABs are not available. There is little sense in keeping this code, especially since it requires supporting a bunch of platform-specific assembly.
Additional testing:
tier1
tier1
tier1
Apart from x86 and AArch64, I only verified the cross-compilation builds pass, no other testing is done.
I did not touch the JVMCI interfaces, since I am not sure what is the proper protocol for JVMCI changes.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk pull/9576/head:pull/9576
$ git checkout pull/9576
Update a local copy of the PR:
$ git checkout pull/9576
$ git pull https://git.openjdk.org/jdk pull/9576/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 9576
View PR using the GUI difftool:
$ git pr show -t 9576
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/9576.diff