<div dir="ltr">Hey guys, <div><br></div><div>Thanks for your insightful responses! We've decided for now to first learn more about how development is done on the analyzer. We are primarily interested in contributing to the development of new checkers, particularly buffer issues (e.g. buffer overflow). Aside from looking at <a href="http://clang-analyzer.llvm.org/potential_checkers.html">http://clang-analyzer.llvm.org/potential_checkers.html</a> and <a href="http://clang-analyzer.llvm.org/checker_dev_manual.html">http://clang-analyzer.llvm.org/checker_dev_manual.html</a>, is there anything else we need to be aware of before we begin development? Also, what is the procedure for getting new checkers approved to add to the list of potential checkers? </div><div><br></div><div>-Ben</div><div><br></div><div class="gmail_extra"><div class="gmail_quote">On Fri, Mar 2, 2018 at 6:41 PM, Artem Dergachev <span dir="ltr"><<a href="mailto:noqnoqneo@gmail.com" target="_blank">noqnoqneo@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Yeah, I guess, The LLVM Foundation might be the right contact for the business/commercial side of things (not sure).<br>
<br>
On the technical side - I'm currently reviewing a large portion of patches for the analyzer. I'd be happy to review and accept any patches, regardless of where they came from - under the usual terms of the LLVM developer policy (you should totally have a look at it). Most importantly, please discuss any non-trivial work before you start coding, and split it up into small incremental patches that gradually improve an experimental feature until it's ready to be turned on by default - this is called "developing under the flag". For example, a new checker will stay in the alpha package during development, and an experimental analyzer core feature will be disabled by an -analyzer-config option. The main point here is to speed up reviews and make sure you don't need to re-do anything - because it's extremely hard to do anything right with LLVM in isolation. Of course, I cannot guarantee that any particular patch is going to be accepted, at least not before I see it.<div class="gmail-HOEnZb"><div class="gmail-h5"><br>
<br>
On 02/03/2018 3:17 PM, Jonas Toth via cfe-dev wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Hi,<br>
<br>
no. I dont have any major position, i would just potentially benefit<br>
from the bounties :P<br>
<br>
I dont know who has the power to decide about financial questions, but<br>
the LLVM deciders are most likely involved in it!<br>
<br>
All the best, Jonas :)<br>
<br>
<br>
Am 02.03.2018 um 23:21 schrieb Benjamin Bales:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Hi Jonas!<br>
<br>
Nice to hear from you. We could certainly add clang-tidy to our<br>
roadmap. The primary reason we are interested in improving the clang<br>
static analyzer is because we build our commercial product, CodeAI<br>
(<a href="http://www.mycode.ai" rel="noreferrer" target="_blank">www.mycode.ai</a>), on top of it. I am hiring an internal work force to<br>
enhance the checkers, but I am interesting in exploring open source<br>
alternatives to push forward this work. I have some ideas, but I<br>
think it would be best if we could arrange a phone call next week<br>
sometime to discuss things. Are you the maintainer of this project?<br>
<br>
-Ben<br>
<br>
On Fri, Mar 2, 2018 at 4:59 PM, Jonas Toth via cfe-dev<br>
<<a href="mailto:cfe-dev@lists.llvm.org" target="_blank">cfe-dev@lists.llvm.org</a>> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Hi,<br>
<br>
nice to hear! Would you consider clang-tidy as second part of clangs<br>
static analysis framework as worthwhile, too?<br>
<br>
All the best, Jonas<br>
<br>
<br>
Am 02.03.2018 um 22:48 schrieb Benjamin Bales via cfe-dev:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Greetings Clang Front End Developers!<br>
<br>
My name is Benjamin Bales, and I am the CTO and co-founder of<br>
QbitLogic, a startup company in Atlanta. We are interested in<br>
sponsoring feature bounties to further develop the clang static<br>
analyzer. Can someone recommend me a point of contact with whom I can<br>
open a dialogue? Let me know. Thanks!<br>
<br>
Sincerely,<br>
</blockquote>
______________________________<wbr>_________________<br>
cfe-dev mailing list<br>
<a href="mailto:cfe-dev@lists.llvm.org" target="_blank">cfe-dev@lists.llvm.org</a><br>
<a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev" rel="noreferrer" target="_blank">http://lists.llvm.org/cgi-bin/<wbr>mailman/listinfo/cfe-dev</a><br>
</blockquote>
<br>
</blockquote>
<br>
______________________________<wbr>_________________<br>
cfe-dev mailing list<br>
<a href="mailto:cfe-dev@lists.llvm.org" target="_blank">cfe-dev@lists.llvm.org</a><br>
<a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev" rel="noreferrer" target="_blank">http://lists.llvm.org/cgi-bin/<wbr>mailman/listinfo/cfe-dev</a><br>
</blockquote>
<br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div style="font-size:12.8px">Benjamin Bales</div><div style="font-size:12.8px">Chief Technology Officer</div><div style="font-size:12.8px"><img src="https://media.licdn.com/mpr/mpr/shrink_200_200/AAEAAQAAAAAAAAlpAAAAJGRhNjRiNzc4LWJjNDctNGE2My05NWY1LTY2MDM3Y2YzZTM1OA.png" alt="QbitLogic" width="96" height="96"><br></div><div style="font-size:12.8px">1180 West Peachtree Street, Ste. 2425</div><div style="font-size:12.8px"><span style="font-size:12.8px">Atlanta, GA 30309 </span></div><div style="font-size:12.8px"><span style="font-size:12.8px">470-214-0598</span><br></div><div style="font-size:12.8px"><br></div><div style="font-size:12.8px"><p style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif;color:rgb(0,0,0)"><span style="font-size:10pt;font-family:"Times New Roman",serif;color:navy">CONFIDENTIALITY NOTICE</span></p><p style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif;color:rgb(0,0,0)"><span style="font-size:10pt;font-family:"Times New Roman",serif;color:navy">This e-mail and any files transmitted with it are confidential and are intended solely for the use of the individual or entity to which they are addressed. This communication may contain privileged attorney material or other Property and Confidential matter. If you are not the intended recipient or the person responsible for delivering the e-mail for the intended person, be advised that you have received this e-mail in error and that any use, dissemination, forwarding, printing, or copying of this e-mail is strictly prohibited. If you believe you have received this e-mail in error, please immediately delete this e-mail and notify Benjamin Bales by telephoning <a href="tel:470-214-0598" value="+14705542690" style="color:rgb(17,85,204)" target="_blank">470-214-0598</a>.<br></span></p></div></div></div></div></div></div></div></div></div></div></div>
</div></div>