-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
8307625: Redundant receiver null check in LibraryCallKit::generate_method_call #14542
Conversation
…them with an assert
👋 Welcome back enothum! A progress list of the required criteria for merging this PR into |
Webrevs
|
…in the product version.
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.
@enothum 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 124 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 (@TobiHartmann, @chhagedorn) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
…else only argument(1) is null checked
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 adding the null check as discussed offline together with @TobiHartmann. Looks good!
Just FTR: The intrinsified |
Thanks for the clarifications and reviews! |
/integrate |
/sponsor |
Going to push as commit c3f10e8.
Your commit was automatically rebased without conflicts. |
@TobiHartmann @enothum Pushed as commit c3f10e8. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
The null_check_receiver() calls in generate_method_call are redundant as all callers of generate_method_call already perform this check. For future uses of generate_method_call a new assert is introduced that fails if the caller does not null check the receiver.
Also generally null_check_receiver() should be combined with stopped(), which was not the case here.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/14542/head:pull/14542
$ git checkout pull/14542
Update a local copy of the PR:
$ git checkout pull/14542
$ git pull https://git.openjdk.org/jdk.git pull/14542/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 14542
View PR using the GUI difftool:
$ git pr show -t 14542
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/14542.diff
Webrev
Link to Webrev Comment