[www] r355446 - Add a new GSoC 2019 open project for Clang Static Analyzer.

[Artem Dergachev via llvm-commits]

Author: dergachev
Date: Tue Mar  5 13:20:02 2019
New Revision: 355446

URL: http://llvm.org/viewvc/llvm-project?rev=355446&view=rev
Log:
Add a new GSoC 2019 open project for Clang Static Analyzer.

Modified:
    www/trunk/OpenProjects.html

Modified: www/trunk/OpenProjects.html
URL: http://llvm.org/viewvc/llvm-project/www/trunk/OpenProjects.html?rev=355446&r1=355445&r2=355446&view=diff
==============================================================================
--- www/trunk/OpenProjects.html (original)
+++ www/trunk/OpenProjects.html Tue Mar  5 13:20:02 2019
@@ -26,6 +26,9 @@
       <li><a href="#improve-autocompletion">Improve shell autocompletion
           for Clang</a>
       </li>
+      <li><a href="#analyze-llvm">Apply the Clang Static Analyzer to LLVM-based
+          Projects</a>
+      </li>
     </ul>
     </li>
     <li>
@@ -283,6 +286,43 @@ main <a href="https://developers.google.
   </p>
 </div>
 
+<!-- *********************************************************************** -->
+<div class="www_subsubsection">
+  <a name="analyze-llvm">Apply the Clang Static Analyzer to LLVM-based
+  Projects</a>
+</div>
+<!-- *********************************************************************** -->
+
+<div class="www_text">
+  <p><b>Description of the project:</b>
+	The idea is to improve the Clang Static Analyzer so that it becomes useful
+	for developers that work on Clang and LLVM themselves, as well as on other
+  LLVM-based projects, like Swift. LLVM makes use of C++ language features that
+  the Static Analyzer has not yet been taught to understand. The analyzer also
+  has false positives on some C++ idioms commonly used in the LLVM codebase.
+  </p>
+  <p>
+	The Static Analyzer is already useful for a variety of projects, but in order
+  to reach the "use your own tools" checkpoint, we'd have to classify, debug,
+  and, ideally, eliminate the most common sources of false positives
+  on our code. It would be the best to fix false positives by improving
+  the Static Analyzer itself, but it may also sometimes be feasible to add
+  a few suppressions (such as assertions) within the LLVM source code so that
+  it is easier for both humans and the Analyzer to understand what's going on.
+  And, of course, it's great to report and maybe even fix the true positives
+  that we manage to find!
+  </p>
+
+  <p><b>Expected results:</b>
+  Results produced by the Analyzer on LLVM itself should become more or
+  less correct: warnings are useful, false alarms are gone. This lets
+  more and more LLVM developers adopt the Static Analyzer in their daily lifes
+  or CI workflows.
+  </p>
+
+  <p><b>Confirmed Mentor:</b> Artem Dergachev, Ravi Kandhadai Madhavan</p>
+  <p><b>Desirable skills:</b> Intermediate knowledge of C++.</p>
+</div>
 
 
 <!-- *********************************************************************** -->