<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Nov 30, 2018, at 2:10 AM, Gábor Horváth via cfe-dev <<a href="mailto:cfe-dev@lists.llvm.org" class="">cfe-dev@lists.llvm.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div class=""><div class="">Hi!<br class=""><br class="">I do see the value of having a consistent format across all clang project's documentation. But a more important aspect is to have better visibility.<br class=""></div>Right now we have analyzer related documentation:<br class=""></div>* In docs/analyzer folder<br class=""></div><div class="">* At the analyzer's homepage<br class="">* lib/StaticAnalyzer/README.txt<br class=""></div><div class="">* The checker in 24 hour talk<br class=""></div><div class="">* We have <a href="https://github.com/haoNoQ/clang-analyzer-guide" class="">https://github.com/haoNoQ/clang-analyzer-guide</a><br class=""><br class=""></div><div class="">Having one updated place as a single source of truth would be a great QoL improvement which could make it easier to get started with the analyzer.<br class=""></div><div class="">I think the lack of such place is one of the biggest obstacles for newcomers.<br class=""><br class=""></div><div class="">Having a more consistent style of documentation with clang tidy for the individual checkers is also a plus from the user's point of view.<br class=""></div><div class="">The current per checker documentation at the analyzer's homepage is often lacking. They are great for getting an idea what a check is about but they do not cover all of the detected cases, do not cover configuration options and do not give the user any advice how to actually solve the problems and what is the best way to suppress potential false positives.<br class=""><br class=""></div><div class="">BTW, are there any users who rely on the analyzer distribution on the analyzer's homepage rather than the analyzer within a clang distribution?</div></div></div></div></div></blockquote><div><br class=""></div><div>I vaguely recall hearing that it comes from the days when the analyzer was not readily available within Clang.</div><div>Right now it’s severely out of date, and IMO should be removed.</div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div class=""> If we do not support that separate distribution I would rather remove it from the analyzer's homepage regardless of the decision of moving the site to the common format.<br class=""></div><div class=""><br class=""></div><div class="">Regards,<br class=""></div><div class="">Gabor<br class=""></div><div dir="ltr" class=""><div class=""><div class=""> <br class=""></div></div></div></div></div></div><br class=""><div class="gmail_quote"><div dir="ltr" class="">On Tue, 13 Nov 2018 at 16:50, Dániel Krupp via cfe-dev <<a href="mailto:cfe-dev@lists.llvm.org" class="">cfe-dev@lists.llvm.org</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang="EN-US" link="#0563C1" vlink="#954F72" class="">
<div class="m_7987779587301843633WordSection1"><p class="MsoNormal">Dear Analyzer Community,<u class=""></u><u class=""></u></p><p class="MsoNormal"><u class=""></u> <u class=""></u></p><p style="margin-right:0in;margin-bottom:9.0pt;margin-left:0in;background:white" class="">
<span style="font-size: 10pt; font-family: "Segoe UI", sans-serif;" class="">Most standard Clang tools (ThreadSanitizer, MemorySanitizer, DataFlowSanitizer etc.)<br class="">
have documentation delivered with Clang and build using Sphinx tool at <a href="https://clang.llvm.org/docs/" target="_blank" class=""><span style="color:#136cb2" class="">https://clang.llvm.org/docs/</span></a>.<br class="">
I thought it would be great to have the ClangSA docs there too in sphinx markup.<u class=""></u><u class=""></u></span></p><p style="margin-right:0in;margin-bottom:9.0pt;margin-left:0in;background:white;font-variant-ligatures:normal;font-variant-caps:normal;text-decoration-style:initial;text-decoration-color:initial;word-spacing:0px" class="">
<span style="font-size: 10pt; font-family: "Segoe UI", sans-serif;" class="">I created a patch
<a href="https://reviews.llvm.org/D54429" target="_blank" class="">https://reviews.llvm.org/D54429</a> where analyzer's documentation main page and the checker sub-pages are<br class="">
transformed into Sphinx RST.<u class=""></u><u class=""></u></span></p><p style="margin-right:0in;margin-bottom:9.0pt;margin-left:0in;background:white" class="">
<span style="font-size: 10pt; font-family: "Segoe UI", sans-serif;" class="">This is how it looks like now:<u class=""></u><u class=""></u></span></p><p style="margin-right:0in;margin-bottom:9.0pt;margin-left:0in;background:white" class="">
<span style="font-size: 10pt; font-family: "Segoe UI", sans-serif;" class=""><a href="http://cc.elte.hu/clang-docs/docs/html/ClangStaticAnalyzer.html" target="_blank" class=""><span style="color:#136cb2" class="">http://cc.elte.hu/clang-docs/docs/html/ClangStaticAnalyzer.html</span></a><u class=""></u><u class=""></u></span></p><p style="margin-right:0in;margin-bottom:9.0pt;margin-left:0in;background:white;font-variant-ligatures:normal;font-variant-caps:normal;text-decoration-style:initial;text-decoration-color:initial;word-spacing:0px" class="">
<span style="font-size: 10pt; font-family: "Segoe UI", sans-serif;" class="">Advantages:<u class=""></u><u class=""></u></span></p><p class="MsoNormal" style="margin-left:22.5pt;line-height:20.4pt;background:white">
<u class=""></u><span style="font-size: 10pt; font-family: Symbol;" class=""><span class="">·<span style="font:7.0pt "Times New Roman"" class="">
</span></span></span><u class=""></u><span style="font-size: 10pt; font-family: "Segoe UI", sans-serif;" class="">The documentation is easier to be maintained in Sphinx markup compared to raw HTML<u class=""></u><u class=""></u></span></p><p class="MsoNormal" style="margin-left:22.5pt;line-height:20.4pt;background:white">
<u class=""></u><span style="font-size: 10pt; font-family: Symbol;" class=""><span class="">·<span style="font:7.0pt "Times New Roman"" class="">
</span></span></span><u class=""></u><span style="font-size: 10pt; font-family: "Segoe UI", sans-serif;" class="">The documentation is easier found in the standard clang doc tree<u class=""></u><u class=""></u></span></p><p class="MsoNormal" style="margin-left:22.5pt;line-height:20.4pt;background:white">
<u class=""></u><span style="font-size: 10pt; font-family: Symbol;" class=""><span class="">·<span style="font:7.0pt "Times New Roman"" class="">
</span></span></span><u class=""></u><span style="font-size: 10pt; font-family: "Segoe UI", sans-serif;" class="">The generated documentation looks nicer ;)<u class=""></u><u class=""></u></span></p><p class="MsoNormal"><br class="">
What was also missing (for many users) is the documentation of the checkers. Similar to the one-pagers what we have for clang-tidy:
<a href="http://clang.llvm.org/extra/clang-tidy/checks/list.html" target="_blank" class="">http://clang.llvm.org/extra/clang-tidy/checks/list.html</a><br class="">
<br class="">
<span style="font-size: 10pt; font-family: "Segoe UI", sans-serif;" class="">So a similar listing page is created:
<a href="http://cc.elte.hu/clang-docs/docs/html/analyzer/checkers.html" target="_blank" class="">http://cc.elte.hu/clang-docs/docs/html/analyzer/checkers.html</a><br class="">
With a specific one-pager example: <a href="http://cc.elte.hu/clang-docs/docs/html/analyzer/checkers/UninitializedObject.html" target="_blank" class="">
<span style="color:#136cb2" class="">http://cc.elte.hu/clang-docs/docs/html/analyzer/checkers/UninitializedObject.html</span></a></span><u class=""></u><u class=""></u></p><p style="margin-right:0in;margin-bottom:9.0pt;margin-left:0in;background:white" class="">
<span style="font-size: 10pt; font-family: "Segoe UI", sans-serif;" class=""><br class="">
In practice the pages can be migrated one by one (after sanitizing them) and at end a redirection can be set up at
<a href="https://clang-analyzer.llvm.org/" target="_blank" class="">https://clang-analyzer.llvm.org/</a></span><span style="font-size:10.0pt;font-family:"Segoe UI",sans-serif" class="">.<span style="" class=""><u class=""></u><u class=""></u></span></span></p><p style="margin-right:0in;margin-bottom:9.0pt;margin-left:0in;background:white" class="">
<span style="font-size: 10pt; font-family: "Segoe UI", sans-serif;" class="">I wonder what you guys think about this approach?<br class="">
</span><br class="">
Thanks,<br class="">
Daniel<u class=""></u><u class=""></u></p>
</div>
</div>
_______________________________________________<br class="">
cfe-dev mailing list<br class="">
<a href="mailto:cfe-dev@lists.llvm.org" target="_blank" class="">cfe-dev@lists.llvm.org</a><br class="">
<a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev" rel="noreferrer" target="_blank" class="">http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev</a><br class="">
</blockquote></div>
_______________________________________________<br class="">cfe-dev mailing list<br class=""><a href="mailto:cfe-dev@lists.llvm.org" class="">cfe-dev@lists.llvm.org</a><br class="">http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev<br class=""></div></blockquote></div><br class=""></body></html>