From: John Criswell <criswell@uiuc.edu>
Date: Fri, 10 Oct 2003 19:50:53 +0000 (+0000)
Subject: Renamed the feature subtests so that they do not begin with 'f'.  It was
X-Git-Url: http://plrg.eecs.uci.edu/git/?p=oota-llvm.git;a=commitdiff_plain;h=a1f7cac0273ce871e14bba597a9ad0838fff143d

Renamed the feature subtests so that they do not begin with 'f'.  It was
never necessary to do that to denote them as feature tests.
Removed the Feature.asm tests as they are the same as the Feature.mc
tests.


git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@9039 91177308-0d34-0410-b5e6-96231b3b80d8
---

diff --git a/docs/TestingGuide.html b/docs/TestingGuide.html
index bf740cf9da3..05af6bcecbb 100644
--- a/docs/TestingGuide.html
+++ b/docs/TestingGuide.html
@@ -222,7 +222,7 @@
 		These are the feature tests found in llvm/test/Feature.  They are broken
 		up into the following categories:
 		<ul>
-			<li>fad<br>
+			<li>ad<br>
 			Assembler/Disassembler tests.  These tests verify that a piece of
 			LLVM assembly language can be assembled into bytecode and then
 			disassembled into the original assembly language code.
@@ -232,24 +232,19 @@
 			can be assembled correctly.
 			<p>
 
-			<li>fasm<br>
-			Assembler tests.  These tests verify that the code can be translated
-			into native assembly code.
-			<p>
-
-			<li>fopt<br>
+			<li>opt<br>
 			Optimizer tests.  These tests verify that two of the
 			optimizer passes completely optimize a program (i.e.
 			after a single pass, they cannot optimize a program
 			any further).
 			<p>
 
-			<li>fmc<br>
+			<li>mc<br>
 			Machine code tests.  These tests verify that the LLVM assembly
 			language file can be translated into native assembly code.
 			<p>
 
-			<li>fcc<br>
+			<li>cc<br>
 			C code tests.  These tests verify that the specified LLVM assembly
 			code can be converted into C source code using the C backend.
 		</ul>