Because D28023 wasn't enough, as i've just seen an assertion-like macro with as many as 12 CFG blocks (including do..while(false) loops), i mocked up a quick CFG depth-first search to easily detect blocks dominated by noreturn blocks.
Details
Details
- Reviewers
zaks.anna dcoughlin xazax.hun a.sidorin - Commits
- rG4e9942662940: [analyzer] Further improve suppress-on-sink behavior in incomplete analyses.
rC308957: [analyzer] Further improve suppress-on-sink behavior in incomplete analyses.
rL308957: [analyzer] Further improve suppress-on-sink behavior in incomplete analyses.
Diff Detail
Diff Detail
Event Timeline
Comment Actions
Just a minor nit.
lib/StaticAnalyzer/Core/BugReporter.cpp | ||
---|---|---|
3332 | The check for visited can be placed into the loop below so we won't even add such blocks to the worklist. |
cfe/trunk/lib/StaticAnalyzer/Core/BugReporter.cpp | ||
---|---|---|
3313 ↗ | (On Diff #108024) | Do you really mean "is dominated by"? That is, "every path from the entry to N's block goes through a no-return block"? Or do you mean "the exit block is not reachable from N's block"? |
The check for visited can be placed into the loop below so we won't even add such blocks to the worklist.