[PATCH] D12358: [Analyzer] Handling constant bound loops

[Ted Kremenek via cfe-commits]

> On Aug 26, 2015, at 3:59 AM, Sean Eveson via cfe-commits <cfe-commits at lists.llvm.org> wrote:
> 
> We have been looking at the following problem, where any code after the constant bound loop is not analyzed because of the limit on how many times the same block is visited, as described in bugzillas #7638 and #23438. This problem is of interest to us because we have identified significant bugs that the checkers are not locating. We have been discussing a solution involving ranges as a longer term project, but I would like to propose a patch to improve the current implementation.

FWIW, I do think this is a great problem to work on.  It is easy to come up with solutions that work for specific examples but fall over on general code.  I completely agree that failing to analyzing code after the loop is a major hole and lost opportunity to find bugs, but fixing that should not be at a tradeoff of a huge influx in false positives.  Some basic invalidation of values touched by the loop, which includes possibly invalidating checker state, will likely be necessary.  I think this is what Anna was getting to in her comment.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-commits/attachments/20150826/62cf34f6/attachment.html>