as Heading elements instead of

. H1 ... doc_title H2 ... doc_section H3 ... doc_subsection H4 ... doc_subsubsection llvm-svn: 129736 --- llvm/docs/TestingGuide.html | 87 ++++++++++++++++++++++++--------------------- 1 file changed, 46 insertions(+), 41 deletions(-) (limited to 'llvm/docs/TestingGuide.html') diff --git a/llvm/docs/TestingGuide.html b/llvm/docs/TestingGuide.html index 5886c85242c..3d6aa92ffb1 100644 --- a/llvm/docs/TestingGuide.html +++ b/llvm/docs/TestingGuide.html @@ -7,9 +7,9 @@ -

LLVM Testing Infrastructure Guide -

Overview

Overview

@@ -64,7 +64,7 @@ use it, and how to add and run tests.

Requirements

@@ -76,7 +76,7 @@ as Python 2.4 or later.

LLVM testing infrastructure organization

@@ -92,7 +92,7 @@ in subversion.

Regression tests

@@ -119,7 +119,7 @@ application or benchmark.

Test suite

@@ -144,8 +144,7 @@ generates code.

Debugging Information -tests

Debugging Information tests

@@ -161,7 +160,7 @@ test suite for more information . This test suite is located in the

Quick start

@@ -179,7 +178,7 @@ the test-suite directory will be automatically configured. Alternatively, you can configure the test-suite module manually.

Regression tests

To run all of the LLVM regression tests, use master Makefile in the llvm/test directory:

@@ -240,7 +239,7 @@ script which is built as part of LLVM. For example, to run the 'lit' man page.

Test suite

To run the comprehensive test suite (tests that compile and execute whole @@ -292,8 +291,7 @@ that subdirectory.

Debugging Information -tests

Debugging Information tests

@@ -312,7 +310,7 @@ clang/test directory.

Regression test structure

The LLVM regression tests are driven by 'lit' and are located in @@ -339,7 +337,7 @@ clang/test directory.

Writing new regression tests

The regression test structure is very simple, but does require some @@ -493,7 +491,7 @@ negatives).

The FileCheck utility

@@ -565,8 +563,9 @@ file.

The FileCheck -check-prefix option

+ The FileCheck -check-prefix option +

@@ -599,8 +598,9 @@ both 32-bit and 64-bit code generation.

The "CHECK-NEXT:" directive

+ The "CHECK-NEXT:" directive +

@@ -639,8 +639,9 @@ directive in a file.

The "CHECK-NOT:" directive

+ The "CHECK-NOT:" directive +

@@ -669,8 +670,9 @@ define i8 @coerce_offset0(i32 %V, i32* %P) {

FileCheck Pattern Matching Syntax

+ FileCheck Pattern Matching Syntax +

@@ -701,8 +703,9 @@ braces explicitly from the input, you can use something ugly like

FileCheck Variables

+ FileCheck Variables +

@@ -740,8 +743,7 @@ define two separate CHECK lines that match on the same line.

Variables and -substitutions

Variables and substitutions

With a RUN line there are a number of substitutions that are permitted. In @@ -836,7 +838,7 @@ substitutions

Other Features

To make RUN line writing easier, there are several shell scripts located @@ -894,8 +896,7 @@ substitutions

Test suite -Structure

Test suite Structure

@@ -963,7 +964,7 @@ will help you separate benign warnings from actual test failures.

Running the test suite

@@ -1024,8 +1025,9 @@ the test code or configure script changes).

-Configuring External Tests

+ Configuring External Tests +

@@ -1056,8 +1058,9 @@ the test code or configure script changes).

-Running different tests

+ Running different tests +

In addition to the regular "whole program" tests, the test-suite @@ -1079,8 +1082,9 @@ LLVM.

-Generating test output

+ Generating test output +

There are a number of ways to run the tests and generate output. The most @@ -1110,8 +1114,9 @@ LLVM.

-Writing custom tests for the test suite

+ Writing custom tests for the test suite +

-- cgit v1.2.3