-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
8323122: AArch64: Increase itable stub size estimate #17336
Conversation
👋 Welcome back linade! A progress list of the required criteria for merging this PR into |
Can I get a review on this small patch please : ) |
@linade 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 101 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. As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@theRealAph, @eastig) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
@theRealAph Do you mind sponsoring this change? Thank you. /integrate |
I think the patch is fine, but @eastig should also take a look. |
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.
lgtm
@linade This is not the first time estimates are updated. JDK-8207343 was implemented to automate vtable/itable stub size calculation. I think it needs improvements. I created JDK-8323741. |
@eastig Thank you for reviewing. It seems to me that the size calculation can not be easily automated. But the overflow prevention might be, by somehow relocating the stubs (not sure if it's common or possible in hotspot). |
/sponsor |
Going to push as commit 36f4b34.
Your commit was automatically rebased without conflicts. |
Since JDK-8307352, itable stub size has grown by 20 bytes on linux-aarch64. In particular, the "slop-counted" code increases from 100->120 bytes, where the current estimate is 124 bytes. I haven't found a case where it exceeds the estimate. For now this size is stable across the few linux-aarch64 configurations I ran with. It doesn't vary (for example) by different klass decoding schemes. But I think the idea of the estimate is that we can never know. I propose we increase the estimate to be safe.
Passed hotspot/jtreg/:tier1
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/17336/head:pull/17336
$ git checkout pull/17336
Update a local copy of the PR:
$ git checkout pull/17336
$ git pull https://git.openjdk.org/jdk.git pull/17336/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 17336
View PR using the GUI difftool:
$ git pr show -t 17336
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/17336.diff
Webrev
Link to Webrev Comment