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
33 lines
728 B
C
33 lines
728 B
C
// RUN: %clang_analyze_cc1 -Wno-array-bounds -analyzer-checker=core,alpha.security.ArrayBound -verify %s
|
|
// XFAIL: *
|
|
|
|
// Once we better handle modeling of sizes of VLAs, we can pull this back
|
|
// into outofbound.c.
|
|
|
|
void sizeof_vla(int a) {
|
|
if (a == 5) {
|
|
char x[a];
|
|
int y[sizeof(x)];
|
|
y[4] = 4; // no-warning
|
|
y[5] = 5; // expected-warning{{out-of-bound}}
|
|
}
|
|
}
|
|
|
|
void sizeof_vla_2(int a) {
|
|
if (a == 5) {
|
|
char x[a];
|
|
int y[sizeof(x) / sizeof(char)];
|
|
y[4] = 4; // no-warning
|
|
y[5] = 5; // expected-warning{{out-of-bound}}
|
|
}
|
|
}
|
|
|
|
void sizeof_vla_3(int a) {
|
|
if (a == 5) {
|
|
char x[a];
|
|
int y[sizeof(*&*&*&x)];
|
|
y[4] = 4; // no-warning
|
|
y[5] = 5; // expected-warning{{out-of-bound}}
|
|
}
|
|
}
|