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
8264395: WB_EnqueueInitializerForCompilation fails with "method holder must be initialized" when called for uninitialized class #3757
Conversation
… must be initialized when called for uninitialized class
👋 Welcome back rraghavan! A progress list of the required criteria for merging this PR into |
@r-v-raghav The following label will be automatically applied to this pull request:
When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command. |
/label remove hotspot |
@r-v-raghav |
@r-v-raghav |
…r must be initialized" when called for uninitialized class
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!
Webrevs
|
@r-v-raghav 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 86 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 |
@r-v-raghav 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 32 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 |
test/hotspot/jtreg/compiler/whitebox/TestEnqueueInitializerForCompilation.java
Outdated
Show resolved
Hide resolved
test/hotspot/jtreg/compiler/whitebox/TestEnqueueInitializerForCompilation.java
Outdated
Show resolved
Hide resolved
test/hotspot/jtreg/compiler/whitebox/TestEnqueueInitializerForCompilation.java
Outdated
Show resolved
Hide resolved
test/hotspot/jtreg/compiler/whitebox/TestEnqueueInitializerForCompilation.java
Outdated
Show resolved
Hide resolved
public class TestEnqueueInitializerForCompilation { | ||
|
||
public static void main(String[] args) { | ||
WhiteBox.getWhiteBox().enqueueInitializerForCompilation(LongWrapper.class, 4); |
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.
What if compilation level 4 (= C2) is not available?
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.
Found unavailable/bad comp levels handled in WhiteBox::compile_method() or later in CompileBroker::compile_method.
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.
Right but wouldn't we hit an assert there if C2 is not available?
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.
For the case scenario mentioned found that the test simply displays a WB whitebox error that is ignored.
So seems we can go ahead with the current test case itself. Thanks
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.
Yes, as we've discussed off-thread, that's fine. Thanks for investigating.
…r must be initialized" when called for uninitialized class
Thank you @TobiHartmann for the comment suggestions. Please note now tried revising the fix for further review. |
/integrate |
@r-v-raghav Since your change was applied there have been 86 commits pushed to the
Your commit was automatically rebased without conflicts. Pushed as commit 3554dc2. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
https://bugs.openjdk.java.net/browse/JDK-8264395
Reported assert failure, during compilation triggered by Whitebox API
enqueueInitializerForCompilation
method,is fixed by adding support to to bail out if a class not initialized yet.
Confirmed the new
compiler/whitebox/TestEnqueueInitializerForCompilation.java
test passes with the proposedwhitebox.cpp
changes and fails with reported assert without this fix.No issues with tier tests.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/3757/head:pull/3757
$ git checkout pull/3757
Update a local copy of the PR:
$ git checkout pull/3757
$ git pull https://git.openjdk.java.net/jdk pull/3757/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 3757
View PR using the GUI difftool:
$ git pr show -t 3757
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/3757.diff