Changes in directory llvm/docs:
TestingGuide.html updated: 1.39 -> 1.40
---
Log message:
Describe llvm/test more accurately given recent changes.
---
Diffs of the changes: (+22 -14)
TestingGuide.html | 36 ++++++++++++++++++++++--------------
1 files changed, 22 insertions(+), 14 deletions(-)
Index: llvm/docs/TestingGuide.html
diff -u llvm/docs/TestingGuide.html:1.39 llvm/docs/TestingGuide.html:1.40
--- llvm/docs/TestingGuide.html:1.39 Fri Aug 11 18:27:02 2006
+++ llvm/docs/TestingGuide.html Thu Feb 8 11:00:55 2007
@@ -216,19 +216,27 @@
subtrees of the test suite directory tree are as follows:</p>
<ul>
-<li><tt>llvm/test/Features</tt>
-<p>This directory contains sample codes that test various features of the
-LLVM language. These pieces of sample code are run through various
-assembler, disassembler, and optimizer passes.</p>
-</li>
-
-<li><tt>llvm/test/Regression</tt>
-<p>This directory contains regression tests for LLVM. When a bug is found
-in LLVM, a regression test containing just enough code to reproduce the
-problem should be written and placed somewhere underneath this directory.
-In most cases, this will be a small piece of LLVM assembly language code,
-often distilled from an actual application or benchmark.</p>
-</li>
+ <li><tt>llvm/test</tt>
+ <p>This directory contains a large array of small tests
+ that exercise various features of LLVM and to ensure that regressions do not
+ occur. The directory is broken into several sub-directories, each focused on
+ a particular area of LLVM. A few of the important ones are:<ul>
+ <li><tt>Analysis</tt>: checks Analysis passes.</li>
+ <li><tt>Archive</tt>: checks the Archive library.</li>
+ <li><tt>Assembler</tt>: checks Assembly reader/writer functionality.</li>
+ <li><tt>Bytecode</tt>: checks Bytecode reader/writer functionality.</li>
+ <li><tt>CodeGen</tt>: checks code generation and each target.</li>
+ <li><tt>Features</tt>: checks various features of the LLVM language.</li>
+ <li><tt>Linker</tt>: tests bytecode linking.</li>
+ <li><tt>Transforms</tt>: tests each of the scalar, IPO, and utility
+ transforms to ensure they make the right transformations.</li>
+ <li><tt>Verifier</tt>: tests the IR verifier.</li>
+ </ul></p>
+ <p>Typically when a bug is found in LLVM, a regression test containing
+ just enough code to reproduce the problem should be written and placed
+ somewhere underneath this directory. In most cases, this will be a small
+ piece of LLVM assembly language code, often distilled from an actual
+ application or benchmark.</p></li>
<li><tt>llvm-test</tt>
<p>The <tt>llvm-test</tt> CVS module contains programs that can be compiled
@@ -630,7 +638,7 @@
John T. Criswell, Reid Spencer, and Tanya Lattner<br>
<a href="http://llvm.org";>The LLVM Compiler Infrastructure</a><br/>
- Last modified: $Date: 2006/08/11 23:27:02 $
+ Last modified: $Date: 2007/02/08 17:00:55 $
</address>
</body>
</html>
_______________________________________________
llvm-commits mailing list
llvm-commits@cs.uiuc.edu
http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits
