-
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
8322159: ThisEscapeAnalyzer crashes for erroneous code #17118
Conversation
👋 Welcome back jlahoda! A progress list of the required criteria for merging this PR into |
Hi @lahodaj, Looks good to me - thanks for 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 sensible
@lahodaj 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 83 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 |
/backport jdk22 |
/integrate |
@lahodaj Backport for repo |
Going to push as commit 7455b1b.
Your commit was automatically rebased without conflicts. |
Creating backport for repo openjdk/jdk22 on branch master /backport openjdk/jdk22 master |
@openjdk[bot] @lahodaj the backport was successfully created on the branch backport-lahodaj-7455b1b5 in my personal fork of openjdk/jdk22. To create a pull request with this backport targeting openjdk/jdk22:master, just click the following link: The title of the pull request is automatically filled in correctly and below you find a suggestion for the pull request body:
If you need to update the source branch of the pull then run the following commands in a local clone of your personal fork of openjdk/jdk22:
|
/backport jdk22u |
@lahodaj the backport was successfully created on the branch backport-lahodaj-7455b1b5 in my personal fork of openjdk/jdk22u. To create a pull request with this backport targeting openjdk/jdk22u:master, just click the following link: The title of the pull request is automatically filled in correctly and below you find a suggestion for the pull request body:
If you need to update the source branch of the pull then run the following commands in a local clone of your personal fork of openjdk/jdk22u:
|
When an unresolvable method is used in the code, the model is a bit strange (and not very easy to fix) - for method invocations, the symbol used is actually a
ClassSymbol
instead ofMethodSymbol
, and method references have fields likekind
unfilled.This is causing issues in ThisEscapeAnalyzer when there were unresolvable methods, and the analyzer is called (i.e. in practice when running with
-Xlint:this-escape -XDshould-stop.at=FLOW
, or similar):visitApply
has a hardcoded cast toMethodSymbol
. Seems the case in not really necessary, so the proposal is to remove it.visitReference
crashes on an access toJCMemberReference.kind
, as it is unfilled. The proposal is to skip the check if the method reference's type is errneous.Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/17118/head:pull/17118
$ git checkout pull/17118
Update a local copy of the PR:
$ git checkout pull/17118
$ git pull https://git.openjdk.org/jdk.git pull/17118/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 17118
View PR using the GUI difftool:
$ git pr show -t 17118
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/17118.diff
Webrev
Link to Webrev Comment