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
8280473: CI: Support unresolved JVM_CONSTANT_Dynamic constant pool entries #7423
Conversation
|
Webrevs
|
Not a review, but I've tested this and can confirm it resolves the bailout issue as reported in the mail thread linked to in JDK-8280473. |
Thanks for validating the fix, Eirik. |
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 reasonable. I just had a few questions (inline comments).
@iwanowww This change now passes all automated pre-integration checks. 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 39 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.
|
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 great!
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!
Thanks for the reviews, Dean, Claes, and Nils. /integrate |
Going to push as commit 88fc3bf.
Your commit was automatically rebased without conflicts. |
Properly support unresolved CONSTANT_Dynamic CP entries in C1/C2.
Right now, both compilers bail out the compilation when they encounter a single unresolved dynamic constant. It forces users to do eager resolution which defeats the whole purpose of using dynamic constants.
The patch is focused on C1 and enables code patching for dynamic constants, but there are minor C2-specific changes to avoid compilation bailouts there.
Testing: hs-tier1 - hs-tier4
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/7423/head:pull/7423
$ git checkout pull/7423
Update a local copy of the PR:
$ git checkout pull/7423
$ git pull https://git.openjdk.java.net/jdk pull/7423/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 7423
View PR using the GUI difftool:
$ git pr show -t 7423
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/7423.diff