Only opt out from it in the few configs where there still are build
warnings.
Details
- Reviewers
ldionne • Quuxplusone Mordante - Group Reviewers
Restricted Project - Commits
- rG7420cf1b1556: [libcxx] [ci] Enable LIBCXX_ENABLE_WERROR where possible
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
I think you should put the -DLIBCXX_ENABLE_WERROR=NO in the cmake cache files. Why isn't there a cmake cache file for generic-gcc @ldionne?
There’s probably none, because no specific configuration is needed.
I don’t think we should involve the cmake cache files regarding LIBCXX_ENABLE_WERROR overall. Also, I think a command line argument (when enabled in run-buildbot) overrides what’s set in a cache file.
And I don’t think we should be enabling that option anywhere in the cache files. When building libcxx with the intent of *using* the library, we don’t want LIBCXX_ENABLE_WERROR enabled, because if it builds successfully, it’s probably fine to use even if it produced warnings. Enabling it should be strictly a CI thing (and when developing the library , if such a setup is wanted).
I prefer not to for the reasons @mstorsjo mentioned. I love using -Werror, but I feel it should always be an opt-in.
I want to see the CI green before approving.
Yep, I noticed that there were some more warnings in the Ryu code. (I had tested building with clang-cl for aarch64, where those warnings weren't present.) I'll soon post a patch that should silence them.