-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
8346751: Internal java compiler error with type annotations in constants expression in constant fields #23029
Conversation
…nts expression in constant fields
…ld inits.
👋 Welcome back jlahoda! A progress list of the required criteria for merging this PR into |
@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 122 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.
looks good
/integrate |
Going to push as commit 0395593.
Your commit was automatically rebased without conflicts. |
Consider code like:
When processing this code, when
Attr.visitVarDef
is called for the field, it will first callAnnotate.queueScanTreeAndTypeAnnotate
on the initializer expression, which will find and attribute type annotations. Then the initializer is attributed, and eventuallyAnnotate.annotateTypeSecondStage
is called on the annotated type (@Nullable String
). This second stage depends on the type annotations being already attributed. This works OK.The problem appears when the code like changed to be like:
In this code, the field is a constant, and it is used from the annotation before
Attr.visitVarDef
is called on the constant. This will trigger attribution of the constant initializer (Attr.attribLazyConstantValue
), which will trigger theAnnotate.annotateTypeSecondStage
on the annotated type, butAnnotate.queueScanTreeAndTypeAnnotate
was not yet called on the initializer, and so the type annotations are not attributed yet, and javac crashes with an exception like:The proposed solution herein is to make sure
Annotate.queueScanTreeAndTypeAnnotate
is called before attributing field initializers inAttr.attribLazyConstantValue
. A flag is used to make sure it is invoked at most once per field.Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/23029/head:pull/23029
$ git checkout pull/23029
Update a local copy of the PR:
$ git checkout pull/23029
$ git pull https://git.openjdk.org/jdk.git pull/23029/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 23029
View PR using the GUI difftool:
$ git pr show -t 23029
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/23029.diff
Using Webrev
Link to Webrev Comment