<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<meta name="x_Generator" content="Microsoft Word 15 (filtered medium)">
<style>
<!--
p.x_MsoNormal, li.x_MsoNormal, div.x_MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif}
a:x_link, span.x_MsoHyperlink
{color:blue;
text-decoration:underline}
a:x_visited, span.x_MsoHyperlinkFollowed
{color:#954F72;
text-decoration:underline}
.x_MsoChpDefault
{}
div.x_WordSection1
{}
-->
</style>
<div lang="EN-GB" link="blue" vlink="#954F72">
<div class="x_WordSection1">
<p class="x_MsoNormal">Thanks for the reply, my usage scenario is for ide integration rather than an end user. I understand that not all checks emit visits, but for those that do how does xcode capture this information?</p>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal">Sent from my Windows 10 phone</p>
<p class="x_MsoNormal"> </p>
<div style="border:none; border-top:solid #E1E1E1 1.0pt; padding:3.0pt 0cm 0cm 0cm">
<p class="x_MsoNormal" style="border:none; padding:0cm"><b>From: </b><a href="mailto:noqnoqneo@gmail.com">Artem Dergachev</a><br>
<b>Sent: </b>25 May 2017 07:39<br>
<b>To: </b><a href="mailto:dan@walms.co.uk">Dan Walmsley</a>; <a href="mailto:cfe-dev@lists.llvm.org">
cfe-dev@lists.llvm.org</a><br>
<b>Subject: </b>Re: [cfe-dev] Is it possible to get static analyzer fixits via libclang?</p>
</div>
<p class="x_MsoNormal"> </p>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">Static analyzer doesn't currently produce fixits, because classes of
<br>
bugs it finds ("path-sensitive" bug reports that take a lot of different <br>
source code locations into account, such as memory leak paths or null <br>
dereference paths) are quite different in nature from normal warnings <br>
issued by the compiler or lint tools like clang-tidy, and most of them <br>
are very hard to reasonably fix automatically.<br>
<br>
<br>
The analyzer also doesn't work when the translation unit has errors, <br>
which seems to be your case (missing semicolon?).<br>
<br>
<br>
I'd also hint that using the scan-build tool instead of adding --analyze <br>
manually is usually easier for bigger projects.<br>
<br>
<br>
<br>
On 5/24/17 11:37 PM, Dan Walmsley via cfe-dev wrote:<br>
><br>
> Hi,<br>
><br>
><br>
> Is it possible to get the fixits that clang-tidy can produce, but <br>
> via libclang?<br>
><br>
><br>
> I tried adding the --analyze option when creating the translation <br>
> unit, but I don't see any static analyser warnings and only fixit I <br>
> have seen so far is to add missing semi colon.<br>
><br>
><br>
> Thanks in advance<br>
><br>
><br>
> Dan<br>
><br>
><br>
><br>
> _______________________________________________<br>
> cfe-dev mailing list<br>
> cfe-dev@lists.llvm.org<br>
> <a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev">http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev</a><br>
<br>
</div>
</span></font>
</body>
</html>