-
Notifications
You must be signed in to change notification settings - Fork 6.2k
8352731: Compiler workaround to forcibly set "-Xlint:-options" can be removed #24309
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 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 787 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 label 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 list. If you would like to change these labels, use the /label pull request command. |
|
Thanks for the review! |
|
/integrate |
|
Going to push as commit e604bb9.
Your commit was automatically rebased without conflicts. |
|
@archiecobbs Pushed as commit e604bb9. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Back in 2011, in order to prevent repeated warnings about bootclasspath not being set (JDK-7022337), code was added to
JavaCompiler.javato forcibly set the-Xlint:-optionsflag after compiler startup:This workaround complicates logic relating to warnings in the
"options"category and, due to improvements to the compiler design since then, it's no longer needed to actually fix the problem. So it can be removed.As a separate cleanup, the field
optionsCheckingInitiallyDisabledinJavaCompiler.javais no longer used and so it can also be removed.Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/24309/head:pull/24309$ git checkout pull/24309Update a local copy of the PR:
$ git checkout pull/24309$ git pull https://git.openjdk.org/jdk.git pull/24309/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 24309View PR using the GUI difftool:
$ git pr show -t 24309Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/24309.diff
Using Webrev
Link to Webrev Comment