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
8236490: Compiler bug relating to @NonNull annotation #2060
Conversation
|
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
@lgxbslgx This change now passes all automated pre-integration checks. 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 207 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 (@vicente-romero-oracle, @jbf) but any other Committer may sponsor as well.
|
/integrate |
@vicente-romero-oracle Could I get your help to sponsor this patch? Thanks a lot. |
@lgxbslgx can you rebase on a fresh upstream and I'll sponsor this for you |
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.
I think is still trying to be way to clever with compressing the different states into previously 1 int and now 2 ints. However this is an improvement and fixes an issue we have.
@jbf Thank you. The patch can be integrated directly because the robot doesn't remind of conflict. |
/sponsor |
@jbf @lgxbslgx Since your change was applied there have been 207 commits pushed to the
Your commit was automatically rebased without conflicts. Pushed as commit 23edb6f. |
Hi all,
If the exception class index in constant pool exceeds 256, the
exception_index
inTypeAnnotationPosition
will not work as expected. Please see the following code:If
catchType
> 256, which means the 8-15 bits is useful, the-((catchType | startPos << 8) + 1);
would override these bits.This patch separates the
startPos
into a new fieldexceptionStartPos
to solve the bug. And a test case is added.Thank you for taking the time to review.
Best Regards.
Progress
Issue
Reviewers
Download
$ git fetch https://git.openjdk.java.net/jdk pull/2060/head:pull/2060
$ git checkout pull/2060