[www] r296522 - Add one extra LLVM Core project to the list of open-projects

Mehdi Amini via llvm-commits llvm-commits at lists.llvm.org
Tue Feb 28 13:27:35 PST 2017


Author: mehdi_amini
Date: Tue Feb 28 15:27:35 2017
New Revision: 296522

URL: http://llvm.org/viewvc/llvm-project?rev=296522&view=rev
Log:
Add one extra LLVM Core project to the list of open-projects

Modified:
    www/trunk/OpenProjects.html

Modified: www/trunk/OpenProjects.html
URL: http://llvm.org/viewvc/llvm-project/www/trunk/OpenProjects.html?rev=296522&r1=296521&r2=296522&view=diff
==============================================================================
--- www/trunk/OpenProjects.html (original)
+++ www/trunk/OpenProjects.html Tue Feb 28 15:27:35 2017
@@ -13,6 +13,7 @@
 	  <li><a href="#hashmap_codegen_mismatch">Changing hashmap iteration order should not change the generated code</a></li>
 	  <li><a href="#opt_remarks">We need better optimization remarks!</a></li>
 	  <li><a href="#llvmir_dump">Smarter way of dumping LLVM IR with -emit-after-all</a></li>
+	  <li><a href="#codegen_testing">Improve code generation testing</a></li>
     </ul>
     <ul><a href="http://clang.llvm.org/">Clang</a>
       <li><a href="#clang-template-instantiation-sugar">Extend clang AST to
@@ -202,6 +203,53 @@ Welcome prospective Google Summer of Cod
   </p>
 </div>
 
+<!-- *********************************************************************** -->
+<div class="www_subsubsection">
+  <a name="codegen_testing">Improve code generation testing</a>
+</div>
+<!-- *********************************************************************** -->
+
+<div class="www_text">
+  <p><b>Description of the project:</b>
+	  After instruction selection LLVM uses the MI (Machine Instruction)
+	  representation for programs. We recently added support for reading and
+	  writing this representation to disk
+	  (http://llvm.org/docs/MIRLangRef.html). Usage of this format for writing
+	  tests is growing and so is the desire to improve the format, tools and
+	  workflow. Improvements would be welcome:
+
+	  <ul><li>Create a single consistent format instead of the current mix of
+		  YAML + IR + MIR</ul></li>
+	  <ul><li>Do not print unnecessary information (we often print default
+		  values where the reader could deduce them)</ul></li>
+	  <ul><li>The format of things like MachineInstr/MachineBasicBlock::dump()
+		  should be the same or very close to the .mir format => change the dump
+		  functions.</ul></li>
+	  <ul><li>Allow the representation to deduce successors of a basic block in
+		  common cases</ul></li>
+	  <ul><li>Allow symbolic names instead of just numbers for virtual
+		  registers</ul></li>
+	  <ul><li>Helper passes: Strip IR information, rename blocks and values, 
+		  debug information, ...</ul></li>
+	  <ul><li>Create a bugpoint mode (or a new tool) to reduce .mir test cases</ul></li>
+	  <ul><li>Write recommendations and guides for .mir based tests</ul></li>
+  </p>
+  
+   <p><b>Contact Person:</b>Matthias Braun</p>
+</div>
+
+
+<!-- *********************************************************************** -->
+<div class="www_subsubsection">
+  <a name=""></a>
+</div>
+<!-- *********************************************************************** -->
+
+<div class="www_text">
+  <p><b>Description of the project:</b>
+  </p>
+</div>
+
 <!-- *********************************************************************** -->
 <div class="www_subsection">
   <a>Clang</a>




More information about the llvm-commits mailing list