-
Notifications
You must be signed in to change notification settings - Fork 10.5k
[Build] Disable -Wdocumentation #72747
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
LLVM doesn't have this warning enabled, so we end up with a whole tonne of warnings from the LLVM headers.
@swift-ci please smoke test |
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'm fine with removing it, but I do wonder why this was enabled in the first place.
@akyrtzi seems like you added this back in 2013 (bf25dde). How do you feel about it being removed? The only real alternative I can think of would be to have all our LLVM include paths as system, though I suspect that would have unintended side effects. Otherwise there's the whack-a-mole game we could play with fixing upstream as these come in. Or a RFC to try get it enabled generally. |
Thank you! These warnings have been polluting the Swift build quite a bit, and I don't think there's a point in having them if LLVM is not also going to be built with the flag to prevent the problems from occurring upstream. |
I assume I added it because LLVM had it enabled then, if LLVM doesn't have it enabled then I agree to remove it. Interestingly, I see upstream commits about fixing |
Might have it locally like we do 😅? I definitely don't see a |
They're all from Apple folks, so I suspect the problems are just being noticed downstream and fixed upstream to quite builds. |
LLVM doesn't have this warning enabled, so we end up with a whole tonne of warnings from the LLVM headers.