[www] r324198 - Patch by Vedant Kumar. Add more projects.

Tanya Lattner via llvm-commits llvm-commits at lists.llvm.org
Sun Feb 4 10:28:18 PST 2018


Author: tbrethou
Date: Sun Feb  4 10:28:17 2018
New Revision: 324198

URL: http://llvm.org/viewvc/llvm-project?rev=324198&view=rev
Log:
Patch by Vedant Kumar. Add more projects.


Modified:
    www/trunk/OpenProjects.html

Modified: www/trunk/OpenProjects.html
URL: http://llvm.org/viewvc/llvm-project/www/trunk/OpenProjects.html?rev=324198&r1=324197&r2=324198&view=diff
==============================================================================
--- www/trunk/OpenProjects.html (original)
+++ www/trunk/OpenProjects.html Sun Feb  4 10:28:17 2018
@@ -10,9 +10,15 @@
       <ul>
   	    <li><a href="#codegen_testing2018">Improve code generation testing</a></li>
       </ul>
+      <ul>
+  	    <li><a href="#llvm_optimized_debugging">Improve debugging of optimized code</a></li>
+      </ul>
     </li>
     <li>
     <a href="http://lldb.llvm.org/"><b>LLDB</b></a><ul>
+      <li><a href="#lldb-data-formatters">Implement a DSL for LLDB data formatters</a>
+      </li>
+
       <li><a href="#lldb-reimplement-lldb-mi">Reimplement lldb-mi on top of the
           LLDB public API</a>
       </li>
@@ -202,6 +208,23 @@ main <a href="https://developers.google.
 
 <!-- *********************************************************************** -->
 <div class="www_subsubsection">
+  <a name="lldb-data-formatters">Implement a DSL for LLDB data formatters</a>
+</div>
+<!-- *********************************************************************** -->
+
+<div class="www_text">
+  <p><b>Description of the project: </b> LLDB's data formatters allow it to pretty-print objects such as std::vector (from the C++ standard library), or String (from the Swift standard library). These data formatters are implemented in C++ and reside within the debugger, but the data structures are defined in other projects. This means that when the data structures change, lldb's data formatters may not be updated in sync. This also means that it's difficult for projects to define and test custom data formatters for special kinds of objects.  </p>
+  <p><b>Expected results: </b> The goal of this project would be to define a DSL which makes it possible to implement lldb data formatters for standard C++ containers. These formatters would be moved into libc++ and tested there. </p>
+  <p><b>Confirmed Mentor:</b> Vedant Kumar and Davide Italiano</p>
+
+  <p><b>Desirable skills:</b>
+    Intermediate knowledge of C++.
+  </p>
+</div>
+
+
+<!-- *********************************************************************** -->
+<div class="www_subsubsection">
   <a name="lldb-reimplement-lldb-mi">Reimplement lldb-mi on top of the LLDB
     public SB API.</a>
 </div>
@@ -287,6 +310,24 @@ main <a href="https://developers.google.
 </div>
 
 <!-- *********************************************************************** -->
+<div class="www_subsubsection">
+  <a name="llvm_optimized_debugging">Improve debugging of optimized code</a>
+</div>
+<!-- *********************************************************************** -->
+
+<div class="www_text">
+  <p>
+  <b>Description of the project:</b> Debugging optimized code can be frustrating. Variables may appear as "<value optimized out>" in the debugger, or may not appear at all. Line numbers in stack traces may disappear, or worse, become inaccurate. To improve the situation, we have to teach more LLVM optimization passes how to preserve debug info. The primary focus will be on mid-level IR passes which fail to pass verification by the <a href="https://reviews.llvm.org/D40512">Debugify utility</a>. This utility can identify passes which drop debug info in a targeted way and can simplify test case generation.
+  </p>
+  <p><b>Expected Results:</b>This project has two goals. Initially, the student will gather metrics on debug info loss for individual llvm passes. This will let us measure subsequent improvements. The second goal is to incrementally fix as many debug info loss bugs as possible, with a focus on areas of the compiler which are the hottest.</p>
+
+  <p><b>Confirmed Mentor:</b> Vedant Kumar and Davide Italiano</p>
+  <p><b>Desirable skills:</b> Intermediate knowledge of C++.</p>
+</div>
+
+
+
+<!-- *********************************************************************** -->
 <div class="www_sectiontitle">
   <a name="gsoc17">Google Summer of Code 2017</a>
 </div>




More information about the llvm-commits mailing list