mirror of
https://github.com/llvm/llvm-project.git
synced 2025-04-26 05:56:07 +00:00
ffe7950ebc
I'm trying to remove unused options from the `Analyses.def` file, then merge the rest of the useful options into the `AnalyzerOptions.def`. Then make sure one can set these by an `-analyzer-config XXX=YYY` style flag. Then surface the `-analyzer-config` to the `clang` frontend; After all of this, we can pursue the tablegen approach described https://discourse.llvm.org/t/rfc-tablegen-clang-static-analyzer-engine-options-for-better-documentation/61488 In this patch, I'm proposing flag deprecations. We should support deprecated analyzer flags for exactly one release. In this case I'm planning to drop this flag in `clang-16`. In the clang frontend, now we won't pass this option to the cc1 frontend, rather emit a warning diagnostic reminding the users about this deprecated flag, which will be turned into error in clang-16. Unfortunately, I had to remove all the tests referring to this flag, causing a mass change. I've also added a test for checking this warning. I've seen that `scan-build` also uses this flag, but I think we should remove that part only after we turn this into a hard error. Reviewed By: martong Differential Revision: https://reviews.llvm.org/D126215
18 lines
610 B
C
18 lines
610 B
C
// RUN: %clang_analyze_cc1 -analyzer-checker=core,alpha.core -Werror %s -verify
|
|
// RUN: %clang_analyze_cc1 -analyzer-checker=core,alpha.core -Werror %s -analyzer-werror -verify=werror
|
|
|
|
// This test case illustrates that using '-analyze' overrides the effect of
|
|
// -Werror. This allows basic warnings not to interfere with producing
|
|
// analyzer results.
|
|
|
|
char* f(int *p) {
|
|
return p; // expected-warning{{incompatible pointer types}} \
|
|
werror-warning{{incompatible pointer types}}
|
|
}
|
|
|
|
void g(int *p) {
|
|
if (!p) *p = 0; // expected-warning{{null}} \
|
|
werror-error{{null}}
|
|
}
|
|
|