Describe llvm/test more accurately given recent changes.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@34055 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
Reid Spencer 2007-02-08 17:00:55 +00:00
parent a05eaa658e
commit a99256e34e

View File

@ -216,19 +216,27 @@ module.</p>
subtrees of the test suite directory tree are as follows:</p> subtrees of the test suite directory tree are as follows:</p>
<ul> <ul>
<li><tt>llvm/test/Features</tt> <li><tt>llvm/test</tt>
<p>This directory contains sample codes that test various features of the <p>This directory contains a large array of small tests
LLVM language. These pieces of sample code are run through various that exercise various features of LLVM and to ensure that regressions do not
assembler, disassembler, and optimizer passes.</p> occur. The directory is broken into several sub-directories, each focused on
</li> a particular area of LLVM. A few of the important ones are:<ul>
<li><tt>Analysis</tt>: checks Analysis passes.</li>
<li><tt>llvm/test/Regression</tt> <li><tt>Archive</tt>: checks the Archive library.</li>
<p>This directory contains regression tests for LLVM. When a bug is found <li><tt>Assembler</tt>: checks Assembly reader/writer functionality.</li>
in LLVM, a regression test containing just enough code to reproduce the <li><tt>Bytecode</tt>: checks Bytecode reader/writer functionality.</li>
problem should be written and placed somewhere underneath this directory. <li><tt>CodeGen</tt>: checks code generation and each target.</li>
In most cases, this will be a small piece of LLVM assembly language code, <li><tt>Features</tt>: checks various features of the LLVM language.</li>
often distilled from an actual application or benchmark.</p> <li><tt>Linker</tt>: tests bytecode linking.</li>
</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> <li><tt>llvm-test</tt>
<p>The <tt>llvm-test</tt> CVS module contains programs that can be compiled <p>The <tt>llvm-test</tt> CVS module contains programs that can be compiled