DKLoehr wrote:

Thanks for contributing to LLVM! We've started to see the warning fire a lot 
more in chromium builds due to the extended coverage. Can we move the new 
functionality behind a separate flag (e.g. `-Wunused-but-set-global` or 
similar) so that we can suppress just the new instances of the warning without 
losing coverage for non-globals? That sort of separate flag helps a lot with 
migrations as we investigate and fix our issues.

https://github.com/llvm/llvm-project/pull/178342
_______________________________________________
cfe-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

Reply via email to