-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
8316907: Fix nonnull-compare warnings #15927
Conversation
👋 Welcome back djelinski! A progress list of the required criteria for merging this PR into |
@djelinski 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. |
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.
@djelinski 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 69 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 |
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.
Thank you, this looks good to me.
Thanks for the reviews! /integrate |
Going to push as commit 516cfb1.
Your commit was automatically rebased without conflicts. |
@djelinski Pushed as commit 516cfb1. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Please review this patch that fixes nonnull-compare warnings emitted by GCC after removing
-fno-delete-null-pointer-checks
.The changes are pretty straightforward:
assert(this)
only changes the behavior of debug code; assertion failure in that place would result in a crash later on,CodeBuffer::print
is a bit more complex to review; fortunately all uses exceptprint_buf_locs
are in CodeBuffer, andprint_buf_locs
is only used by developers from debugger.I verified tier1-5 tests, just in case. No new failures.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/15927/head:pull/15927
$ git checkout pull/15927
Update a local copy of the PR:
$ git checkout pull/15927
$ git pull https://git.openjdk.org/jdk.git pull/15927/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 15927
View PR using the GUI difftool:
$ git pr show -t 15927
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/15927.diff
Webrev
Link to Webrev Comment