-
Notifications
You must be signed in to change notification settings - Fork 6.1k
8320272: Make method_entry_barrier address shared #16708
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
Conversation
|
👋 Welcome back kvn! A progress list of the required criteria for merging this PR into |
Webrevs
|
|
Arm (32-bit) cross build is broken by recent changes 8301997 |
|
/cc hotspot-compiler |
|
@vnkozlov |
|
This seems fine, but you could explain a little more why this is useful for Leyden? I would think having StubRoutines::method_entry_barrier() would be enough, and that it could reference the existing platform-specific name, minimizing changes. I don't understand why the storage needs to be shared in StubRoutines::_method_entry_barrier, for example. |
Thank you for looking, Dean. Yes, your suggestion would work too. Leyden code calls StubRoutines::method_entry_barrier() to get address: SCCache.cpp#L3337 |
| AMD64_ONLY(nmethod_entry_barrier = StubRoutines::x86::method_entry_barrier()); | ||
| AARCH64_ONLY(nmethod_entry_barrier = StubRoutines::aarch64::method_entry_barrier()); | ||
| AMD64_ONLY(nmethod_entry_barrier = StubRoutines::method_entry_barrier()); | ||
| AARCH64_ONLY(nmethod_entry_barrier = StubRoutines::method_entry_barrier()); |
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.
Now that's there's a single name you can remove the 2 per arch definitions in favor of single assignment statement.
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.
Done.
|
@vnkozlov 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 21 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 |
|
@vnkozlov : Hi, I have tested this on linux-riscv platform. Result looks fine. |
|
Thank you, @RealFYang, for testing. I applied your patch. |
|
/integrate |
|
Going to push as commit c4aba87.
Your commit was automatically rebased without conflicts. |
Currently all platforms have declared their own address variable for method_entry_barrier stub. Some have even slightly different name: nmethod_entry_barrier. For Leyden project one address is preferable.
In aarch64 code changed
movptrtoleainstruction to get relocation info as on x86.Tested x86 and aarch64, tier1-4, xcomp, stress. I need help to test on other platforms. Thanks!
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/16708/head:pull/16708$ git checkout pull/16708Update a local copy of the PR:
$ git checkout pull/16708$ git pull https://git.openjdk.org/jdk.git pull/16708/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 16708View PR using the GUI difftool:
$ git pr show -t 16708Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/16708.diff
Webrev
Link to Webrev Comment