[all-commits] [llvm/llvm-project] 9da697: Reland "[analyzer] Deprecate the unused 'analyzer-...
Balazs Benics via All-commits
all-commits at lists.llvm.org
Tue Jun 14 01:23:13 PDT 2022
Author: Balazs Benics <balazs.benics at sigmatechnology.se>
Date: 2022-06-14 (Tue, 14 Jun 2022)
Reland "[analyzer] Deprecate the unused 'analyzer-opt-analyze-nested-blocks' cc1 flag"
It was previously reverted by 8406839d1926486de900c7cabeea9f841bd3edf2.
This flag was introduced by
Author: Ted Kremenek <kremenek at apple.com>
Date: Mon Dec 7 22:06:12 2009 +0000
Add clang-cc option '-analyzer-opt-analyze-nested-blocks' to treat
block literals as an entry point for analyzer checks.
The last reference was removed by this commit:
Author: Anna Zaks <ganna at apple.com>
Date: Fri Dec 21 01:19:15 2012 +0000
[analyzer] Add blocks and ObjC messages to the call graph.
This paves the road for constructing a better function dependency graph.
If we analyze a function before the functions it calls and inlines,
there is more opportunity for optimization.
Note, we add call edges to the called methods that correspond to
function definitions (declarations with bodies).
Consequently, we should remove this dead flag.
However, this arises a couple of burning questions.
- Should the `cc1` frontend still accept this flag - to keep
tools/users passing this flag directly to `cc1` (which is unsupported,
- If we should remain backward compatible, how long?
- How can we get rid of deprecated and obsolete flags at some point?
Reviewed By: martong
Differential Revision: https://reviews.llvm.org/D126067
More information about the All-commits