[cfe-dev] Static Analyzer (annotations, path sensitive analysis)
Gábor Kozár
kozargabor at gmail.com
Fri May 31 06:43:13 PDT 2013
Hi,
There was some discussion several weeks ago about implementing a
generalized attribute for the static analyzer. You should look it up, as I
recall, it touched the same subjects you're interested in. I do not think
any of it is implemented yet though.
> *Using the scan-build which checkers are enabled by default?*
*
*
Any checkers that are not experimental. See
lib/StaticAnalyzer/Checkers/Checkers.td for the classification of the
checkers.
*
*
Gabor*
*
2013/5/31 Orbán György <o.gyorgy at gmail.com>
>
> Hi all!
>
> Are there any other or newer possibilities to suppress a specific analyzer
> warning?
> I checked the FAQ and there are two possibilities right now
> - analyzer annotations
> - __clang_analzyer__ macro
>
> I'm interested in C++ code analysis. I found some annotations at the clang
> analyzer webpage but if I understand it right for C++ I can only use the
> attribute nonnull or anlyzer_noreturn. Are there other source code
> annotation I could use?
> Is it possible to create some annotation which will suppress only warnings
> for a given check?
> Using the scan-build which checkers are enabled by default?
>
> My last question is in connection with the path sensitive analysis. Could
> you give me some details how the exploded graph exploration is made or
> where can i find some information about it? The traversal is made parallel
> for each path?
>
> Thanks in advance!
>
> Best regards,
> George
>
>
>
>
> _______________________________________________
> cfe-dev mailing list
> cfe-dev at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20130531/a4d1bcbc/attachment.html>
More information about the cfe-dev
mailing list