-
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
8294468: Fix char-subscripts warnings in Hotspot #10455
8294468: Fix char-subscripts warnings in Hotspot #10455
Conversation
👋 Welcome back shade! A progress list of the required criteria for merging this PR into |
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. Thanks.
@shipilev 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 45 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.
The GHA failure is unrelated. /integrate |
Going to push as commit ceb5b08.
Your commit was automatically rebased without conflicts. |
There seem to be the only place in Hotspot where this warning fires, yet the warning is disabled wholesale for Hotspot. This is not good.
I can trace the addition of char-subscripts exclusion to JDK-8211029 (Sep 2018). The only place in Hotspot where in fires is present from the initial load (2007).
The underlying problem that this warning tells us about is that
char
might be signed on some platforms, so we can potentially access the negative index. It is not a bug in our current code, that bounds the value ofk
underMAXID-1
, which is19
.Additional testing:
tier1
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk pull/10455/head:pull/10455
$ git checkout pull/10455
Update a local copy of the PR:
$ git checkout pull/10455
$ git pull https://git.openjdk.org/jdk pull/10455/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 10455
View PR using the GUI difftool:
$ git pr show -t 10455
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/10455.diff