diff options
author | Balazs Benics <balazs.benics@sigmatechnology.se> | 2022-06-10 12:57:15 +0200 |
---|---|---|
committer | Balazs Benics <balazs.benics@sigmatechnology.se> | 2022-06-10 12:57:15 +0200 |
commit | d50d9946d1d7e5f20881f0bc71fbd025040b1c96 (patch) | |
tree | 183ae06fa551bf353e2f1c15718de5f771370566 /flang/lib/Frontend/CompilerInvocation.cpp | |
parent | 8b360c69e9e31c38995014414aac523b94b2adaf (diff) | |
download | llvm-d50d9946d1d7e5f20881f0bc71fbd025040b1c96.zip llvm-d50d9946d1d7e5f20881f0bc71fbd025040b1c96.tar.gz llvm-d50d9946d1d7e5f20881f0bc71fbd025040b1c96.tar.bz2 |
[analyzer] Deprecate `-analyzer-store region` flag
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
Diffstat (limited to 'flang/lib/Frontend/CompilerInvocation.cpp')
0 files changed, 0 insertions, 0 deletions