[PATCH] Modeling APIs in the Static Analyzer

Gábor Horváth xazax.hun at gmail.com
Sun Jul 13 06:11:09 PDT 2014

Hi Anna,

Thank you for the review. I have tweaked the test, so it no longer requires
the error reporting tweak that is not done yet to pass. I have also added
some high level comments to some files, if you think some information is
lacking I will add them in the next iteration as well. The BugReporter
patch is now separated into a different patch.

On 11 July 2014 18:02, Anna Zaks <ganna at apple.com> wrote:

> For example, modeling functions should allow you to find bugs and suppress
> false positives outside of those functions. I would suggest adding a few of
> those tests first.
How are the false positives suppressed? I did not find any resource on
that. Found some analyzer attributes but I did not find them suitable for
this purpuse at the first glance. But I think once the locations that are
in a model file are omitted from the report path, the regular methods for
suppressing false positives should work (and I will definitely add test
case to ensure this once it is done).

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-commits/attachments/20140713/fcd14dbc/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: api_modeling.patch
Type: text/x-patch
Size: 37772 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/cfe-commits/attachments/20140713/fcd14dbc/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: bugreporter.patch
Type: text/x-patch
Size: 1728 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/cfe-commits/attachments/20140713/fcd14dbc/attachment-0001.bin>

More information about the cfe-commits mailing list