-
Notifications
You must be signed in to change notification settings - Fork 6.1k
8343479: Remove unnecessary @SuppressWarnings annotations (hotspot) #21853
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
8343479: Remove unnecessary @SuppressWarnings annotations (hotspot) #21853
Conversation
|
👋 Welcome back acobbs! A progress list of the required criteria for merging this PR into |
|
@archiecobbs 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 142 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 |
|
@archiecobbs The following labels will be automatically applied to this pull request:
When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing lists. If you would like to change these labels, use the /label pull request command. |
Webrevs
|
|
Hi @archiecobbs can you please give some more info about why these were introduced, and why they are now not needed any more? |
|
Hi @eme64,
FYI there are several other PR's like this one. I haven't checked exhaustively, but all of the ones I've checked appear to be due to either (a) the warning was never needed, or (b) a subsequent refinement of the warning itself which made the code no longer qualify as "warnable". For an example of (a) see commit 8fb70c7 which added For an example of (b), see commit b431c69 which added In this particular PR, it looks like (for example) the useless I guess the only other possibility is that the warning stopped working at some point due to a bug, but I haven't seen any examples of that. |
Correction - there is actually one case that revealed a compiler bug: JDK-8343286. |
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 reasonable.
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.
Ok, thanks for the explanation. Sounds reasonable.
|
Thanks for the reviews. |
|
/integrate |
|
Going to push as commit 087a07b.
Your commit was automatically rebased without conflicts. |
|
@archiecobbs Pushed as commit 087a07b. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Please review this patch which removes unnecessary
@SuppressWarningsannotations.Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/21853/head:pull/21853$ git checkout pull/21853Update a local copy of the PR:
$ git checkout pull/21853$ git pull https://git.openjdk.org/jdk.git pull/21853/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 21853View PR using the GUI difftool:
$ git pr show -t 21853Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/21853.diff
Using Webrev
Link to Webrev Comment