thakis added a comment.

http://llvm-cs.pcc.me.uk/tools/clang/include/clang/StaticAnalyzer/Core/PathSensitive/CallEvent.h/risInSystemHeader
 suggests that the analyzer has some plumbing for this, so I added dcoughlin as 
reviewer, who has touched some of those lines before. dcoughlin, as background: 
We're playing with running the analyzer on chromium, and we were pretty 
surprised that it defaults to printing diagnostics for system headers. That's 
different from what regular clang does, and there isn't much applications can 
do about diagnostics in system headers. kmarshall wrote a script to manually 
filter out diagnostics from system headers, but we figured it'd make more sense 
if the analyzer didn't emit those diagnostics in the first place -- probably by 
default, but maybe behind some flag. Are you familiar with the design behind 
the current behavior? Does it make sense to change this? Are we missing some 
existing flag?

(kmarshall: In the future, please send some context lines with your diffs, see 
http://llvm.org/docs/Phabricator.html#requesting-a-review-via-the-web-interface.)


Repository:
  rL LLVM

https://reviews.llvm.org/D30593



_______________________________________________
cfe-commits mailing list
cfe-commits@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

Reply via email to