<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><br><div><div>On Aug 29, 2014, at 12:06 , Anna Zaks <<a href="mailto:ganna@apple.com">ganna@apple.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><meta http-equiv="Content-Type" content="text/html charset=us-ascii"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Aug 29, 2014, at 11:48 AM, Ted Kremenek <<a href="mailto:kremenek@apple.com" class="">kremenek@apple.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=us-ascii" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">This looks fine to me, although the list might want a bit more motivation. The idea here is to compose this with "--analyze" so that users can selectively opt out specific files from static analysis.</div></div></div></blockquote>Will add to commit message.<br class=""><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><br class=""></div><div class="">There looks like some unintended changes in the patch:</div><div class=""><br class=""></div><div class=""><div class="">- getInliningModeForFunction(const Decl *D, const SetOfConstDecls &Visited);</div><div class="">+ getInliningModeForFunction(const Decl *D, const SetOfConstDecls &Visited);</div><div class=""> </div></div><div class="">Looks like an unintended indentation change unrelated to this patch.</div><div class=""><br class=""></div></div></div></blockquote><div><br class=""></div><div>The indentation was wrong in the file I was editing, so I've decided to correct. It's unrelated code, but the same file..</div><br class=""><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">Also:</div><div class=""><br class=""></div><div class=""><div class="">+ // Don't analyze if the user explicitely asked for no checks to be performed</div><div class="">+ // on this file.</div></div><div class=""><br class=""></div><div class="">explicitely -> explicitly</div><div class=""><br class=""></div></div></div></blockquote><br class="">Thanks.</div><div><br class=""><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">Can you also add to the test case showing that the option works when the -analyzer-checker and -analyzer-disable-all-checkers are inverted?</div><div class=""><br class=""></div><div class="">For example, take this RUN line:</div><div class=""><br class=""></div><div class="">+// RUN: %clang_cc1 -analyze -analyzer-checker=core -analyzer-store=region -analyzer-disable-all-checks -verify %s</div><div class=""><br class=""></div><div class="">and also add:</div><div class=""><br class=""></div><div class="">+// RUN: %clang_cc1 -analyze -analyzer-disable-all-checks -analyzer-checker=core -analyzer-store=region -verify %s</div><div class=""> </div><div class="">just to show the two behave the same.</div></div></div></blockquote><div><br class=""></div>Will do.</div></div></blockquote><br></div><div>Oooops, Ted's comments reminded me of one more test: %clang --analyze %s -Xanalyzer -analyzer-disable-all-checks. Just to test everything through the driver, which is what we really care about.</div><div><br></div><div>Jordan</div><br></body></html>