-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
8263352: assert(use == polladr) failed: the use should be a safepoint polling #3061
Conversation
👋 Welcome back whuang! A progress list of the required criteria for merging this PR into |
@Wanghuang-Huawei |
@Wanghuang-Huawei |
@Wanghuang-Huawei 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. |
Webrevs
|
I have question for @rwestrel who did strip mining. Looking on nodes I see:
So why Poll's LoadP node's control edge is not the same as SafePoint's control edge? Why it points to inner loop head? |
@@ -0,0 +1,74 @@ | |||
/* |
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.
We don't use bug ID for tests anymore. Rename it to something meaningful and move it to corresponding compiler/loopopts/
or compiler/loopstripmining/
directory.
That makes sense but needs to be done explicitly:
|
Yes, that is it. @rwestrel why you need first clone?
I think we can use original one because it is only used to copy notes in And do we always have this Load? May be runtime check instead of assert? |
Right. It's likely not needed;
That I don't know. |
@Wanghuang-Huawei are you working on Roland's implementation? Or you want us to work on it? |
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.
Okay. Lets push the fix as suggested in match_fill_loop() and new test.
And I will file separate RFE for Roland's changes.
@Wanghuang-Huawei 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 98 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 (@vnkozlov) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
I am not sure if
Thank you for your review. I've renamed the test case (which can also be used as test case of JDK-8264063 ?) and pushed that. |
Thank you for your work ! |
Yes, the test will be very useful for 8264063. The test looks good now. |
/integrate |
@Wanghuang-Huawei |
/sponsor |
@vnkozlov @Wanghuang-Huawei Since your change was applied there have been 98 commits pushed to the
Your commit was automatically rebased without conflicts. Pushed as commit 6e3a158. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
The main reason of this failure has been shown in JDK-8263352.
intrinsify_fill
the array when it is really safe here, so I fix this bug byreturn
other cases.In this patch, I will give a small test case called
Test8263352.java
to reproduct this failure.Thanks to @vnkozlov , who found this failure for the first time (to me).
Thanks to @nsjian,who found the case which can reproduct this failure everytime.
Thanks to @pfustc, who changed notes with us.
Progress
Issue
Reviewers
Contributors
<whuang@openjdk.org>
<wuyan34@huawei.com>
Download
To checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/3061/head:pull/3061
$ git checkout pull/3061
To update a local copy of the PR:
$ git checkout pull/3061
$ git pull https://git.openjdk.java.net/jdk pull/3061/head