-
Notifications
You must be signed in to change notification settings - Fork 6.1k
8343218: Add option to disable allocating interface and abstract classes in non-class metaspace #26579
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 coleenp! A progress list of the required criteria for merging this PR into |
@coleenp 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 55 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 |
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.
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.
Generally looks fine. Stylistic/process note, though: the RFE synopsis still reads that we are disabling the optimization. We are not doing it here, we are only guarding it with a flag. Either submit a new RFE or rename this bug?
Okay, I fixed the titles and will discuss with @vnkozlov and @TobiHartmann next week about getting this into JDK 25 or not. |
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 fine for an added safety-guard. Thanks
Could you please apply the following patch?
|
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.
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
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.
Re-approved.
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.
Let's go!
GHA looks clean |
Going to push as commit da3a5da.
Your commit was automatically rebased without conflicts. |
Thank you Aleksey,Thomas, David, Vladimir and Yudi. |
This change introduces a diagnostic flag to disable the change to allocate interface and abstract Klass metadata in the non-class metaspace. Testing for JDK 25 has completed with this feature in place, but there may be cases where we should disable this. A future change will be to remove this code.
Tested with tier1-4 with the flag off, and 1-4 with the flag on.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/26579/head:pull/26579
$ git checkout pull/26579
Update a local copy of the PR:
$ git checkout pull/26579
$ git pull https://git.openjdk.org/jdk.git pull/26579/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 26579
View PR using the GUI difftool:
$ git pr show -t 26579
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/26579.diff
Using Webrev
Link to Webrev Comment