<div dir="ltr">Yes, I'm mostly interested in hiding issues from those headers (performance is a side benefit).<div><br></div><div>I'll look into the approaches you suggested.</div><div><br></div><div>Thanks very much,</div>
<div>Aemon</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Sep 16, 2013 at 2:02 PM, Anna Zaks <span dir="ltr"><<a href="mailto:ganna@apple.com" target="_blank">ganna@apple.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div>Are you mostly concerned abut performance implications of analyzing third party headers?</div>
<div>One might also not want to show issues reported in those, in which case the black list might also be useful.</div><div><br></div>You could add another option to the analyzer that enables checking only in the project headers. This would be similar to how !AnalyzeAll option works - we just skip the functions defined in headers in AnalysisConsumer. (Note, that if you just wanted to suppress the issues, you could most likely do it from the checker.) <div>
<br></div><div>If you are to add another option, note that we are switching to a new method of defining options - you should not need to modify CompilerInviocation, for example, see "<span style="font-family:Menlo;font-size:14px">shouldReportIssuesInMainSourceFile</span>" .</div>
<span class="HOEnZb"><font color="#888888"><div><br></div><div>Anna.</div></font></span><div><div class="h5"><div><div><br><div><div>On Sep 16, 2013, at 10:40 AM, Aemon Cannon <<a href="mailto:aemoncannon@gmail.com" target="_blank">aemoncannon@gmail.com</a>> wrote:</div>
<br><blockquote type="cite"><div dir="ltr">Hi Anna,<div><br><div>I would be happy with some way to specify a local blacklist. At the moment, once I enable the analyzer-header option, it doesn't seem like I have any sway over which headers the checker is run over. I suspect my checker is doing a lot of extra work grinding through library headers.</div>
<div><br></div><div>(it may help to know that this is an intraprocedural analysis, so I don't care about chasing arguments into libraries)</div><div><br></div><div>Thanks, Aemon<br></div>
<div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Sep 16, 2013 at 1:16 PM, Anna Zaks <span dir="ltr"><<a href="mailto:ganna@apple.com" target="_blank">ganna@apple.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
We don't have a list of known third-party headers anywhere, but having this seems generally useful.<br>
<br>
Anna.<br>
<div>On Sep 14, 2013, at 10:22 PM, Aemon Cannon <<a href="mailto:aemoncannon@gmail.com" target="_blank">aemoncannon@gmail.com</a>> wrote:<br>
<br>
> I'd want to enable analysis of project headers (-analyzer-opt-analyze-headers), but would like to ignore third-party library headers. Currently I have an ad hoc, in-checker, solution to this problem, but was wondering if there's an easier way. Would be nice if there was a blacklist of directories or something.<br>
><br>
> Thanks,<br>
> Aemon<br>
</div>> _______________________________________________<br>
> cfe-dev mailing list<br>
> <a href="mailto:cfe-dev@cs.uiuc.edu" target="_blank">cfe-dev@cs.uiuc.edu</a><br>
> <a href="http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev" target="_blank">http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev</a><br>
<br>
</blockquote></div><br></div></div></div>
</blockquote></div><br></div></div></div></div></div></blockquote></div><br></div>