-
Notifications
You must be signed in to change notification settings - Fork 6.1k
8301630: C2: 8297933 broke type speculation in some cases #12368
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 roland! A progress list of the required criteria for merging this PR into |
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.
Looks good!
|
@rwestrel 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 345 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 |
|
compiler/intrinsics/unsafe/AllocateUninitializedArray.java fails with -XX:TypeProfileLevel=222 |
The reason for that failure is that speculation sees an array type that is exact but of element type top which makes little sense. I added a test case. That happens when an array of some integer type is casted to some other integer type (int[] and short[] in the test case). The result should not be an exact array. I propose fixing |
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 to me. I'll re-run testing and report back.
|
All tests passed. |
|
@TobiHartmann thanks for the review and tests. @chhagedorn 's review was on the previous version of this fix so I'd like another review. Anyone? |
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.
The update looks good to me, too!
|
@chhagedorn thanks for the review. |
|
/integrate |
|
Going to push as commit 6b07243.
Your commit was automatically rebased without conflicts. |
With 8297933, a TypeAryPtr is a lot more likely to have a null _klass
and that breaks TypePtr::speculative_type().
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk pull/12368/head:pull/12368$ git checkout pull/12368Update a local copy of the PR:
$ git checkout pull/12368$ git pull https://git.openjdk.org/jdk pull/12368/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 12368View PR using the GUI difftool:
$ git pr show -t 12368Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/12368.diff