-
Notifications
You must be signed in to change notification settings - Fork 6.2k
8315447: Invalid Type Annotation attached to a method instead of a lambda #24206
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
Conversation
|
👋 Welcome back liach! A progress list of the required criteria for merging this PR into |
|
@liach 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 1 new commit pushed to the
Please see this link for an up-to-date comparison between the source branch of this pull request and the ➡️ To integrate this PR with the above commit message to the |
vicente-romero-oracle
left a comment
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 to me
|
Tier 1-3 tests pass. |
|
Thanks for the reviews! /integrate |
|
Going to push as commit f5a0db4.
Your commit was automatically rebased without conflicts. |
In
LambdaToMethod, when a type annotation is attributed to a lambda's synthetic method or the original method, the annotation's position is queried. However, for container annotations, their positions may not yet be up-to-date, and they are wrongly attributed to the outer method.This bug was discovered because this wrong attribution can bring in an invalid BCI value referring to a lambda method code array that may be out-of-bounds for the outer method. CombinationTargetTest3 had to stay on the old internal proprietary classfile API due to this reason, as the ClassFile API throws an IAE for such a malformed type annotation attribute.
Please review this patch; this is a blocker for the removal of com.sun.tools.classfile from the JDK, which I wish to accomplish when the boot JDK is 24.
Testing: langtools/tools/javac and javap.
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/24206/head:pull/24206$ git checkout pull/24206Update a local copy of the PR:
$ git checkout pull/24206$ git pull https://git.openjdk.org/jdk.git pull/24206/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 24206View PR using the GUI difftool:
$ git pr show -t 24206Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/24206.diff
Using Webrev
Link to Webrev Comment