-
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
8263075: C2: simplify anti-dependence check in PhaseCFG::implicit_null_check() #8684
Conversation
…t_null_check(). JDK-8263075
👋 Welcome back brianjstafford! A progress list of the required criteria for merging this PR into |
@brianjstafford 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
|
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.
Tobias is running testing. Please wait results.
@brianjstafford 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 302 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, @TobiHartmann, @robcasloz) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
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 and tests passed. @robcasloz should also have a look.
Running some additional tests, will come back with the results. |
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.
Thanks for working on this cleanup, @brianjstafford! The loop removal looks good to me, and the additional tests passed, I just have a few comments about the assertions and their documentation.
Thank you @robcasloz for the suggestions, hopefully I've incorporated them as you expected. Please let me know if I should make further changes. |
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.
Thanks for addressing all my comments! I just have a last, style comment on the updated revision.
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.
Thanks for addressing my last comment!
@brianjstafford feel free to mark this PR as ready for integration ( |
The langtools/tier1 failures on Windows x64 are not related to this recent whitespace change, and I'm seeing similar failures on other outstanding PRs. Might be an infrastructure issue. However, I'm not positive if the failures will prevent integration. |
/integrate |
@brianjstafford |
/sponsor |
Going to push as commit c674348.
Your commit was automatically rebased without conflicts. |
@vnkozlov @brianjstafford Pushed as commit c674348. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
The reporter for this issue (https://bugs.openjdk.java.net/browse/JDK-8263075) indicated that there's an assumption that we can rely on that the while loop in question will run exactly one time. Based on this, I've done the following:
while
loopbreak
statements intocontinue
statements. They no longer need to break out of thewhile
loop, now that it's gone. However, they were early exits from thewhile
loop that ended up resulting incontinue
statements for the larger enclosing loop. Thus we can just callcontinue
directly.b
, as we no longer need to traverse the node hierarchy. We can usemb
directly.Passes jdk, langtools, and hotspot Tier 1 tests on Linux (x64 and ARM64) and macOS (x64 and ARM64). Most Tier 1 tests pass on Windows (x64 and ARM64), but there are a handful of failures unrelated to this change.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/8684/head:pull/8684
$ git checkout pull/8684
Update a local copy of the PR:
$ git checkout pull/8684
$ git pull https://git.openjdk.java.net/jdk pull/8684/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 8684
View PR using the GUI difftool:
$ git pr show -t 8684
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/8684.diff