Gitiles
Code Review Sign In
gerrit-public.fairphone.software / toolchain / llvm-project / 04ed1426f65ada3eda61bd870bece25b9bc6227a / . / llvm / docs / TestingGuide.html
blob: 09d08c3356018d110646b5dda5129dfd783b4eb4 [file] [log] [blame]
Misha Brukman773d6f62004-03-01 18:21:04 +0000[diff] [blame]1<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
2 "http://www.w3.org/TR/html4/strict.dtd">
John Criswelle90fc1f2003-10-10 18:42:49 +0000[diff] [blame]3<html>
Brian Gaeke739811d2003-10-23 18:10:28 +0000[diff] [blame]4<head>
Misha Brukman773d6f62004-03-01 18:21:04 +0000[diff] [blame]5 <title>LLVM Test Suite Guide</title>
6 <link rel="stylesheet" href="llvm.css" type="text/css">
Brian Gaeke739811d2003-10-23 18:10:28 +0000[diff] [blame]7</head>
Brian Gaeke739811d2003-10-23 18:10:28 +0000[diff] [blame]8<body>
9
10<div class="doc_title">
11 LLVM Test Suite Guide
12</div>
John Criswelle90fc1f2003-10-10 18:42:49 +0000[diff] [blame]13
Brian Gaeke739811d2003-10-23 18:10:28 +0000[diff] [blame]14<ol>
Reid Spencer49fb40c2004-11-01 08:30:14 +0000[diff] [blame]15 <li><a href="#overview">Overview</a></li>
16 <li><a href="#Requirements">Requirements</a></li>
17 <li><a href="#quick">Quick Start</a></li>
18 <li><a href="#org">LLVM Test Suite Organization</a>
19 <ul>
20 <li><a href="#codefragments">Code Fragments</a></li>
21 <li><a href="#wholeprograms">Whole Programs</a></li>
22 </ul>
23 </li>
24 <li><a href="#tree">LLVM Test Suite Tree</a></li>
Tanya Lattner4d690182004-12-06 02:11:52 +0000[diff] [blame]25 <li><a href="#dgstructure">DejaGNU Structure</a></li>
Reid Spencer49fb40c2004-11-01 08:30:14 +0000[diff] [blame]26 <li><a href="#progstructure"><tt>llvm-test</tt> Structure</a></li>
Chris Lattner17d145e2006-05-23 01:40:20 +0000[diff] [blame]27 <li><a href="#run">Running the LLVM Tests</a>
28 <ul>
29 <li><a href="#customtest">Writing custom tests for llvm-test</a></li>
30 </ul>
31 </li>
Reid Spencer49fb40c2004-11-01 08:30:14 +0000[diff] [blame]32 <li><a href="#nightly">Running the nightly tester</a></li>
Brian Gaeke739811d2003-10-23 18:10:28 +0000[diff] [blame]33</ol>
John Criswelle90fc1f2003-10-10 18:42:49 +0000[diff] [blame]34
Chris Lattner020e1fc2004-05-23 21:07:27 +0000[diff] [blame]35<div class="doc_author">
Tanya Lattner4d690182004-12-06 02:11:52 +0000[diff] [blame]36 <p>Written by John T. Criswell, <a
37 href="http://llvm.x10sys.com/rspencer">Reid Spencer</a>, and Tanya Lattner</p>
Chris Lattner020e1fc2004-05-23 21:07:27 +0000[diff] [blame]38</div>
John Criswelle90fc1f2003-10-10 18:42:49 +0000[diff] [blame]39
Reid Spencerae21b0b2004-09-05 20:07:26 +0000[diff] [blame]40<!--=========================================================================-->
Misha Brukman773d6f62004-03-01 18:21:04 +0000[diff] [blame]41<div class="doc_section"><a name="overview">Overview</a></div>
Reid Spencerae21b0b2004-09-05 20:07:26 +0000[diff] [blame]42<!--=========================================================================-->
John Criswelle90fc1f2003-10-10 18:42:49 +0000[diff] [blame]43
Misha Brukman773d6f62004-03-01 18:21:04 +0000[diff] [blame]44<div class="doc_text">
John Criswelle90fc1f2003-10-10 18:42:49 +0000[diff] [blame]45
Misha Brukman773d6f62004-03-01 18:21:04 +0000[diff] [blame]46<p>This document is the reference manual for the LLVM test suite. It documents
47the structure of the LLVM test suite, the tools needed to use it, and how to add
48and run tests.</p>
John Criswelle90fc1f2003-10-10 18:42:49 +0000[diff] [blame]49
Misha Brukman773d6f62004-03-01 18:21:04 +0000[diff] [blame]50</div>
John Criswelle90fc1f2003-10-10 18:42:49 +0000[diff] [blame]51
Reid Spencerae21b0b2004-09-05 20:07:26 +0000[diff] [blame]52<!--=========================================================================-->
Misha Brukman773d6f62004-03-01 18:21:04 +0000[diff] [blame]53<div class="doc_section"><a name="Requirements">Requirements</a></div>
Reid Spencerae21b0b2004-09-05 20:07:26 +0000[diff] [blame]54<!--=========================================================================-->
John Criswelle90fc1f2003-10-10 18:42:49 +0000[diff] [blame]55
Misha Brukman773d6f62004-03-01 18:21:04 +0000[diff] [blame]56<div class="doc_text">
John Criswelle90fc1f2003-10-10 18:42:49 +0000[diff] [blame]57
Misha Brukman773d6f62004-03-01 18:21:04 +0000[diff] [blame]58<p>In order to use the LLVM test suite, you will need all of the software
59required to build LLVM, plus the following:</p>
John Criswelle90fc1f2003-10-10 18:42:49 +0000[diff] [blame]60
Misha Brukman773d6f62004-03-01 18:21:04 +0000[diff] [blame]61<dl>
Tanya Lattner4d690182004-12-06 02:11:52 +0000[diff] [blame]62<dt><a href="http://www.gnu.org/software/dejagnu/">DejaGNU</a></dt>
63<dd>The Feature and Regressions tests are organized and run by DejaGNU.</dd>
64<dt><a href="http://expect.nist.gov/">Expect</a></dt>
65<dd>Expect is required by DejaGNU.</dd>
Tanya Lattner9a1b8932004-12-08 17:35:31 +0000[diff] [blame]66<dt><a href="http://www.tcl.tk/software/tcltk/">tcl</a></dt>
67<dd>Tcl is required by DejaGNU. </dd>
John Criswelle90fc1f2003-10-10 18:42:49 +0000[diff] [blame]68
Reid Spencer9f16cad2004-11-01 08:26:25 +0000[diff] [blame]69<dt><a href="http://www.netlib.org/f2c">F2C</a></dt>
Misha Brukmaned3dc432004-10-08 00:55:43 +0000[diff] [blame]70<dd>For now, LLVM does not have a Fortran front-end, but using F2C, we can run
71Fortran benchmarks. F2C support must be enabled via <tt>configure</tt> if not
72installed in a standard place. F2C requires three items: the <tt>f2c</tt>
73executable, <tt>f2c.h</tt> to compile the generated code, and <tt>libf2c.a</tt>
74to link generated code. By default, given an F2C directory <tt>$DIR</tt>, the
75configure script will search <tt>$DIR/bin</tt> for <tt>f2c</tt>,
76<tt>$DIR/include</tt> for <tt>f2c.h</tt>, and <tt>$DIR/lib</tt> for
77<tt>libf2c.a</tt>. The default <tt>$DIR</tt> values are: <tt>/usr</tt>,
78<tt>/usr/local</tt>, <tt>/sw</tt>, and <tt>/opt</tt>. If you installed F2C in a
79different location, you must tell <tt>configure</tt>:
80
81<ul>
82<li><tt>./configure --with-f2c=$DIR</tt><br>
83This will specify a new <tt>$DIR</tt> for the above-described search
84process. This will only work if the binary, header, and library are in their
85respective subdirectories of <tt>$DIR</tt>.</li>
86
87<li><tt>./configure --with-f2c-bin=/binary/path --with-f2c-inc=/include/path
88--with-f2c-lib=/lib/path</tt><br>
89This allows you to specify the F2C components separately. Note: if you choose
90this route, you MUST specify all three components, and you need to only specify
91<em>directories</em> where the files are located; do NOT include the
92filenames themselves on the <tt>configure</tt> line.</li>
93</ul></dd>
94</dl>
Jim Laskey27abf2b2006-03-27 18:41:06 +0000[diff] [blame]95
Jim Laskey1677a602006-03-27 19:33:35 +0000[diff] [blame]96<p>Darwin (Mac OS X) developers can simplify the installation of Expect and tcl
97by using fink. <tt>fink install expect</tt> will install both. Alternatively,
Jim Laskeyb0a83ad2006-03-27 19:46:38 +0000[diff] [blame]98Darwinports users can use <tt>sudo port install expect</tt> to install Expect
99and tcl.</p>
Jim Laskeyc1a36f52006-03-27 19:09:44 +0000[diff] [blame]100
Misha Brukman773d6f62004-03-01 18:21:04 +0000[diff] [blame]101</div>
John Criswelle90fc1f2003-10-10 18:42:49 +0000[diff] [blame]102
Reid Spencerae21b0b2004-09-05 20:07:26 +0000[diff] [blame]103<!--=========================================================================-->
Misha Brukman773d6f62004-03-01 18:21:04 +0000[diff] [blame]104<div class="doc_section"><a name="quick">Quick Start</a></div>
Reid Spencerae21b0b2004-09-05 20:07:26 +0000[diff] [blame]105<!--=========================================================================-->
John Criswelle90fc1f2003-10-10 18:42:49 +0000[diff] [blame]106
Misha Brukman773d6f62004-03-01 18:21:04 +0000[diff] [blame]107<div class="doc_text">
Brian Gaeke739811d2003-10-23 18:10:28 +0000[diff] [blame]108
Reid Spencerae21b0b2004-09-05 20:07:26 +0000[diff] [blame]109<p>The tests are located in two separate CVS modules. The basic feature and
110regression tests are in the main "llvm" module under the directory
111<tt>llvm/test</tt>. A more comprehensive test suite that includes whole
112programs in C and C++ is in the <tt>llvm-test</tt> module. This module should
113be checked out to the <tt>llvm/projects</tt> directory. When you
114<tt>configure</tt> the <tt>llvm</tt> module, the <tt>llvm-test</tt> module
Chris Lattner15f17ec2006-05-23 01:25:11 +0000[diff] [blame]115will be automatically configured. Alternatively, you can configure the
116 <tt>llvm-test</tt> module manually.</p>
117<p>To run all of the simple tests in LLVM using DejaGNU, use the master Makefile
118 in the <tt>llvm/test</tt> directory:</p>
Misha Brukman773d6f62004-03-01 18:21:04 +0000[diff] [blame]119<pre>
Reid Spencerae21b0b2004-09-05 20:07:26 +0000[diff] [blame]120% gmake -C llvm/test
Misha Brukman773d6f62004-03-01 18:21:04 +0000[diff] [blame]121</pre>
Tanya Lattner4d690182004-12-06 02:11:52 +0000[diff] [blame]122or<br>
123<pre>
124% gmake check
125</pre>
John Criswell61617f72005-05-13 20:25:49 +0000[diff] [blame]126
127<p>To run only a subdirectory of tests in llvm/test using DejaGNU (ie.
128Regression/Transforms), just set the TESTSUITE variable to the path of the
129subdirectory (relative to <tt>llvm/test</tt>):</p>
Tanya Lattner4d690182004-12-06 02:11:52 +0000[diff] [blame]130<pre>
131% gmake -C llvm/test TESTSUITE=Regression/Transforms
132</pre>
Misha Brukman5da60ba2005-03-10 22:51:59 +0000[diff] [blame]133
John Criswell61617f72005-05-13 20:25:49 +0000[diff] [blame]134<p><b>Note: If you are running the tests with <tt>objdir != subdir</tt>, you
135must have run the complete testsuite before you can specify a
136subdirectory.</b></p>
John Criswelle90fc1f2003-10-10 18:42:49 +0000[diff] [blame]137
Reid Spencerae21b0b2004-09-05 20:07:26 +0000[diff] [blame]138<p>To run the comprehensive test suite (tests that compile and execute whole
139programs), run the <tt>llvm-test</tt> tests:</p>
John Criswelle90fc1f2003-10-10 18:42:49 +0000[diff] [blame]140
Misha Brukman773d6f62004-03-01 18:21:04 +0000[diff] [blame]141<pre>
Reid Spencerae21b0b2004-09-05 20:07:26 +0000[diff] [blame]142% cd llvm/projects
143% cvs co llvm-test
144% cd llvm-test
145% ./configure --with-llvmsrc=$LLVM_SRC_ROOT --with-llvmobj=$LLVM_OBJ_ROOT
146% gmake
Misha Brukman773d6f62004-03-01 18:21:04 +0000[diff] [blame]147</pre>
148
149</div>
150
Reid Spencerae21b0b2004-09-05 20:07:26 +0000[diff] [blame]151<!--=========================================================================-->
Misha Brukman773d6f62004-03-01 18:21:04 +0000[diff] [blame]152<div class="doc_section"><a name="org">LLVM Test Suite Organization</a></div>
Reid Spencerae21b0b2004-09-05 20:07:26 +0000[diff] [blame]153<!--=========================================================================-->
Misha Brukman773d6f62004-03-01 18:21:04 +0000[diff] [blame]154
155<div class="doc_text">
156
157<p>The LLVM test suite contains two major categories of tests: code
Reid Spencerae21b0b2004-09-05 20:07:26 +0000[diff] [blame]158fragments and whole programs. Code fragments are in the <tt>llvm</tt> module
John Criswell61617f72005-05-13 20:25:49 +0000[diff] [blame]159under the <tt>llvm/test</tt> directory. The whole programs
160test suite is in the <tt>llvm-test</tt> module under the main directory.</p>
Misha Brukman773d6f62004-03-01 18:21:04 +0000[diff] [blame]161
162</div>
163
Chris Lattner17d145e2006-05-23 01:40:20 +0000[diff] [blame]164<!-- _______________________________________________________________________ -->
165<div class="doc_subsection"><a name="codefragments">Code Fragments</a></div>
166<!-- _______________________________________________________________________ -->
Misha Brukman773d6f62004-03-01 18:21:04 +0000[diff] [blame]167
168<div class="doc_text">
169
170<p>Code fragments are small pieces of code that test a specific feature of LLVM
171or trigger a specific bug in LLVM. They are usually written in LLVM assembly
172language, but can be written in other languages if the test targets a particular
173language front end.</p>
174
175<p>Code fragments are not complete programs, and they are never executed to
176determine correct behavior.</p>
177
Tanya Lattner4d690182004-12-06 02:11:52 +0000[diff] [blame]178<p>These code fragment tests are located in the <tt>llvm/test/Features</tt> and
Reid Spencerae21b0b2004-09-05 20:07:26 +0000[diff] [blame]179<tt>llvm/test/Regression</tt> directories.</p>
Misha Brukman773d6f62004-03-01 18:21:04 +0000[diff] [blame]180
181</div>
182
Chris Lattner17d145e2006-05-23 01:40:20 +0000[diff] [blame]183<!-- _______________________________________________________________________ -->
Misha Brukman773d6f62004-03-01 18:21:04 +0000[diff] [blame]184<div class="doc_subsection"><a name="wholeprograms">Whole Programs</a></div>
Chris Lattner17d145e2006-05-23 01:40:20 +0000[diff] [blame]185<!-- _______________________________________________________________________ -->
Misha Brukman773d6f62004-03-01 18:21:04 +0000[diff] [blame]186
187<div class="doc_text">
188
189<p>Whole Programs are pieces of code which can be compiled and linked into a
190stand-alone program that can be executed. These programs are generally written
191in high level languages such as C or C++, but sometimes they are written
192straight in LLVM assembly.</p>
Reid Spencerae21b0b2004-09-05 20:07:26 +0000[diff] [blame]193
Misha Brukman773d6f62004-03-01 18:21:04 +0000[diff] [blame]194<p>These programs are compiled and then executed using several different
195methods (native compiler, LLVM C backend, LLVM JIT, LLVM native code generation,
196etc). The output of these programs is compared to ensure that LLVM is compiling
197the program correctly.</p>
198
199<p>In addition to compiling and executing programs, whole program tests serve as
200a way of benchmarking LLVM performance, both in terms of the efficiency of the
201programs generated as well as the speed with which LLVM compiles, optimizes, and
202generates code.</p>
203
Reid Spencerae21b0b2004-09-05 20:07:26 +0000[diff] [blame]204<p>All "whole program" tests are located in the <tt>llvm-test</tt> CVS
205module.</p>
Misha Brukman773d6f62004-03-01 18:21:04 +0000[diff] [blame]206
207</div>
208
Reid Spencerae21b0b2004-09-05 20:07:26 +0000[diff] [blame]209<!--=========================================================================-->
Misha Brukman773d6f62004-03-01 18:21:04 +0000[diff] [blame]210<div class="doc_section"><a name="tree">LLVM Test Suite Tree</a></div>
Reid Spencerae21b0b2004-09-05 20:07:26 +0000[diff] [blame]211<!--=========================================================================-->
Misha Brukman773d6f62004-03-01 18:21:04 +0000[diff] [blame]212
213<div class="doc_text">
214
215<p>Each type of test in the LLVM test suite has its own directory. The major
216subtrees of the test suite directory tree are as follows:</p>
Misha Brukman773d6f62004-03-01 18:21:04 +0000[diff] [blame]217
Reid Spencerae21b0b2004-09-05 20:07:26 +0000[diff] [blame]218<ul>
219<li><tt>llvm/test/Features</tt>
220<p>This directory contains sample codes that test various features of the
221LLVM language. These pieces of sample code are run through various
222assembler, disassembler, and optimizer passes.</p>
223</li>
Misha Brukman773d6f62004-03-01 18:21:04 +0000[diff] [blame]224
Reid Spencerae21b0b2004-09-05 20:07:26 +0000[diff] [blame]225<li><tt>llvm/test/Regression</tt>
226<p>This directory contains regression tests for LLVM. When a bug is found
227in LLVM, a regression test containing just enough code to reproduce the
228problem should be written and placed somewhere underneath this directory.
229In most cases, this will be a small piece of LLVM assembly language code,
230often distilled from an actual application or benchmark.</p>
231</li>
Misha Brukman773d6f62004-03-01 18:21:04 +0000[diff] [blame]232
Reid Spencerae21b0b2004-09-05 20:07:26 +0000[diff] [blame]233<li><tt>llvm-test</tt>
234<p>The <tt>llvm-test</tt> CVS module contains programs that can be compiled
235with LLVM and executed. These programs are compiled using the native compiler
236and various LLVM backends. The output from the program compiled with the
237native compiler is assumed correct; the results from the other programs are
Misha Brukman8d08d362004-10-08 00:41:27 +0000[diff] [blame]238compared to the native program output and pass if they match.</p>
Misha Brukman773d6f62004-03-01 18:21:04 +0000[diff] [blame]239
Reid Spencerae21b0b2004-09-05 20:07:26 +0000[diff] [blame]240<p>In addition for testing correctness, the <tt>llvm-test</tt> directory also
241performs timing tests of various LLVM optimizations. It also records
242compilation times for the compilers and the JIT. This information can be
243used to compare the effectiveness of LLVM's optimizations and code
244generation.</p></li>
John Criswelle90fc1f2003-10-10 18:42:49 +0000[diff] [blame]245
Reid Spencerae21b0b2004-09-05 20:07:26 +0000[diff] [blame]246<li><tt>llvm-test/SingleSource</tt>
247<p>The SingleSource directory contains test programs that are only a single
248source file in size. These are usually small benchmark programs or small
249programs that calculate a particular value. Several such programs are grouped
250together in each directory.</p></li>
251
252<li><tt>llvm-test/MultiSource</tt>
253<p>The MultiSource directory contains subdirectories which contain entire
254programs with multiple source files. Large benchmarks and whole applications
255go here.</p></li>
256
257<li><tt>llvm-test/External</tt>
Misha Brukman8d08d362004-10-08 00:41:27 +0000[diff] [blame]258<p>The External directory contains Makefiles for building code that is external
259to (i.e., not distributed with) LLVM. The most prominent members of this
260directory are the SPEC 95 and SPEC 2000 benchmark suites. The presence and
Reid Spencerae21b0b2004-09-05 20:07:26 +0000[diff] [blame]261location of these external programs is configured by the llvm-test
262<tt>configure</tt> script.</p></li>
263
Misha Brukman773d6f62004-03-01 18:21:04 +0000[diff] [blame]264</ul>
Brian Gaeke739811d2003-10-23 18:10:28 +0000[diff] [blame]265
Misha Brukman773d6f62004-03-01 18:21:04 +0000[diff] [blame]266</div>
Tanya Lattner4d690182004-12-06 02:11:52 +0000[diff] [blame]267<!--=========================================================================-->
268<div class="doc_section"><a name="dgstructure">DejaGNU Structure</a></div>
269<!--=========================================================================-->
270
271<div class="doc_text">
272<p>The LLVM test suite is partially driven by DejaGNU and partially
273driven by GNU Make. Specifically, the Features and Regression tests
John Criswelldfe6a862004-12-10 15:51:16 +0000[diff] [blame]274are all driven by DejaGNU. The <tt>llvm-test</tt>
Tanya Lattner4d690182004-12-06 02:11:52 +0000[diff] [blame]275module is currently driven by a set of Makefiles.</p>
276
277<p>The DejaGNU structure is very simple, but does require some
John Criswelldfe6a862004-12-10 15:51:16 +0000[diff] [blame]278information to be set. This information is gathered via <tt>configure</tt> and
279is written to a file, <tt>site.exp</tt> in <tt>llvm/test</tt>. The
280<tt>llvm/test</tt>
Tanya Lattner4d690182004-12-06 02:11:52 +0000[diff] [blame]281Makefile does this work for you.</p>
282
283<p>In order for DejaGNU to work, each directory of tests must have a
284<tt>dg.exp</tt> file. This file is a program written in tcl that calls
285the <tt>llvm-runtests</tt> procedure on each test file. The
286llvm-runtests procedure is defined in
287<tt>llvm/test/lib/llvm-dg.exp</tt>. Any directory that contains only
288directories does not need the <tt>dg.exp</tt> file.</p>
289
290<p>In order for a test to be run, it must contain information within
291the test file on how to run the test. These are called <tt>RUN</tt>
292lines. Run lines are specified in the comments of the test program
293using the keyword <tt>RUN</tt> followed by a colon, and lastly the
294commands to execute. These commands will be executed in a bash script,
295so any bash syntax is acceptable. You can specify as many RUN lines as
296necessary. Each RUN line translates to one line in the resulting bash
297script. Below is an example of legal RUN lines in a <tt>.ll</tt>
298file:</p>
299<pre>
300; RUN: llvm-as < %s | llvm-dis > %t1
301; RUN: llvm-dis < %s.bc-13 > %t2
302; RUN: diff %t1 %t2
303</pre>
304<p>There are a couple patterns within a <tt>RUN</tt> line that the
305llvm-runtest procedure looks for and replaces with the appropriate
306syntax:</p>
Misha Brukman5da60ba2005-03-10 22:51:59 +0000[diff] [blame]307
308<dl style="margin-left: 25px">
Tanya Lattner4d690182004-12-06 02:11:52 +0000[diff] [blame]309<dt>%p</dt>
310<dd>The path to the source directory. This is for locating
311any supporting files that are not generated by the test, but used by
312the test.</dd>
313<dt>%s</dt>
314<dd>The test file.</dd>
315
Tanya Lattnerd8697042004-12-08 17:37:21 +0000[diff] [blame]316<dt>%t</dt>
Tanya Lattner4d690182004-12-06 02:11:52 +0000[diff] [blame]317<dd>Temporary filename: testscript.test_filename.tmp, where
318test_filename is the name of the test file. All temporary files are
319placed in the Output directory within the directory the test is
320located.</dd>
321
322<dt>%prcontext</dt>
323<dd>Path to a script that performs grep -C. Use this since not all
324platforms support grep -C.</dd>
325
Reid Spencer31bf9a02004-12-22 06:45:24 +0000[diff] [blame]326<dt>%llvmgcc</dt> <dd>Full path to the llvm-gcc executable.</dd>
327<dt>%llvmgxx</dt> <dd>Full path to the llvm-g++ executable.</dd>
Misha Brukman5da60ba2005-03-10 22:51:59 +0000[diff] [blame]328</dl>
Tanya Lattner4d690182004-12-06 02:11:52 +0000[diff] [blame]329
330<p>There are also several scripts in the llvm/test/Scripts directory
331that you might find useful when writing <tt>RUN</tt> lines.</p>
332
333<p>Lastly, you can easily mark a test that is expected to fail on a
Chris Lattner15f17ec2006-05-23 01:25:11 +0000[diff] [blame]334specific platform or with a specific version of llvmgcc by using the
335 <tt>XFAIL</tt> keyword. Xfail lines are
Tanya Lattner4d690182004-12-06 02:11:52 +0000[diff] [blame]336specified in the comments of the test program using <tt>XFAIL</tt>,
337followed by a colon, and one or more regular expressions (separated by
Tanya Lattner1a96c712006-04-20 04:47:55 +0000[diff] [blame]338a comma) that will match against the target triplet or llvmgcc version for the
Chris Lattner15f17ec2006-05-23 01:25:11 +0000[diff] [blame]339machine. You can use * to match all targets. You can specify the major or full
340 version (i.e. 3.4) for llvmgcc. Here is an example of an
Tanya Lattner4d690182004-12-06 02:11:52 +0000[diff] [blame]341<tt>XFAIL</tt> line:</p>
342<pre>
Tanya Lattner79674962006-04-20 04:45:59 +0000[diff] [blame]343; XFAIL: darwin,sun,llvmgcc4
Tanya Lattner4d690182004-12-06 02:11:52 +0000[diff] [blame]344</pre>
345
346</div>
John Criswelle90fc1f2003-10-10 18:42:49 +0000[diff] [blame]347
Reid Spencerae21b0b2004-09-05 20:07:26 +0000[diff] [blame]348<!--=========================================================================-->
Reid Spencerae21b0b2004-09-05 20:07:26 +0000[diff] [blame]349<div class="doc_section"><a name="progstructure"><tt>llvm-test</tt>
350Structure</a></div>
351<!--=========================================================================-->
John Criswelle90fc1f2003-10-10 18:42:49 +0000[diff] [blame]352
Misha Brukman773d6f62004-03-01 18:21:04 +0000[diff] [blame]353<div class="doc_text">
Brian Gaeke739811d2003-10-23 18:10:28 +0000[diff] [blame]354
Misha Brukman8d08d362004-10-08 00:41:27 +0000[diff] [blame]355<p>As mentioned previously, the <tt>llvm-test</tt> module provides three types
356of tests: MultiSource, SingleSource, and External. Each tree is then subdivided
357into several categories, including applications, benchmarks, regression tests,
358code that is strange grammatically, etc. These organizations should be
359relatively self explanatory.</p>
John Criswelle90fc1f2003-10-10 18:42:49 +0000[diff] [blame]360
Misha Brukman8d08d362004-10-08 00:41:27 +0000[diff] [blame]361<p>In addition to the regular "whole program" tests, the <tt>llvm-test</tt>
362module also provides a mechanism for compiling the programs in different ways.
363If the variable TEST is defined on the gmake command line, the test system will
364include a Makefile named <tt>TEST.&lt;value of TEST variable&gt;.Makefile</tt>.
365This Makefile can modify build rules to yield different results.</p>
Misha Brukman773d6f62004-03-01 18:21:04 +0000[diff] [blame]366
Misha Brukman8d08d362004-10-08 00:41:27 +0000[diff] [blame]367<p>For example, the LLVM nightly tester uses <tt>TEST.nightly.Makefile</tt> to
368create the nightly test reports. To run the nightly tests, run <tt>gmake
369TEST=nightly</tt>.</p>
Misha Brukman773d6f62004-03-01 18:21:04 +0000[diff] [blame]370
Misha Brukman8d08d362004-10-08 00:41:27 +0000[diff] [blame]371<p>There are several TEST Makefiles available in the tree. Some of them are
372designed for internal LLVM research and will not work outside of the LLVM
373research group. They may still be valuable, however, as a guide to writing your
374own TEST Makefile for any optimization or analysis passes that you develop with
375LLVM.</p>
Reid Spencercce67552004-12-08 16:52:51 +0000[diff] [blame]376
377<p>Note, when configuring the <tt>llvm-test</tt> module, you might want to
378specify the following configuration options:</p>
379<dl>
380 <dt><i>--enable-spec2000</i>
381 <dt><i>--enable-spec2000=&lt;<tt>directory</tt>&gt;</i>
382 <dd>
383 Enable the use of SPEC2000 when testing LLVM. This is disabled by default
384 (unless <tt>configure</tt> finds SPEC2000 installed). By specifying
385 <tt>directory</tt>, you can tell configure where to find the SPEC2000
386 benchmarks. If <tt>directory</tt> is left unspecified, <tt>configure</tt>
387 uses the default value
388 <tt>/home/vadve/shared/benchmarks/speccpu2000/benchspec</tt>.
389 <p>
390 <dt><i>--enable-spec95</i>
391 <dt><i>--enable-spec95=&lt;<tt>directory</tt>&gt;</i>
392 <dd>
393 Enable the use of SPEC95 when testing LLVM. It is similar to the
394 <i>--enable-spec2000</i> option.
395 <p>
396 <dt><i>--enable-povray</i>
397 <dt><i>--enable-povray=&lt;<tt>directory</tt>&gt;</i>
398 <dd>
399 Enable the use of Povray as an external test. Versions of Povray written
400 in C should work. This option is similar to the <i>--enable-spec2000</i>
401 option.
402</dl>
Misha Brukman773d6f62004-03-01 18:21:04 +0000[diff] [blame]403</div>
404
Reid Spencerae21b0b2004-09-05 20:07:26 +0000[diff] [blame]405<!--=========================================================================-->
Misha Brukman773d6f62004-03-01 18:21:04 +0000[diff] [blame]406<div class="doc_section"><a name="run">Running the LLVM Tests</a></div>
Reid Spencerae21b0b2004-09-05 20:07:26 +0000[diff] [blame]407<!--=========================================================================-->
Misha Brukman773d6f62004-03-01 18:21:04 +0000[diff] [blame]408
409<div class="doc_text">
410
411<p>First, all tests are executed within the LLVM object directory tree. They
Reid Spencerae21b0b2004-09-05 20:07:26 +0000[diff] [blame]412<i>are not</i> executed inside of the LLVM source tree. This is because the
413test suite creates temporary files during execution.</p>
Misha Brukman773d6f62004-03-01 18:21:04 +0000[diff] [blame]414
Chris Lattner15f17ec2006-05-23 01:25:11 +0000[diff] [blame]415<p>The master Makefile in llvm/test is capable of running only the DejaGNU
416driven tests. By default, it will run all of these tests.</p>
Misha Brukman773d6f62004-03-01 18:21:04 +0000[diff] [blame]417
Tanya Lattner9a1b8932004-12-08 17:35:31 +0000[diff] [blame]418<p>To run only the DejaGNU driven tests, run <tt>gmake</tt> at the
John Criswell417cb0a2005-05-13 19:48:07 +0000[diff] [blame]419command line in <tt>llvm/test</tt>. To run a specific directory of tests, use
420the TESTSUITE variable.
Tanya Lattner9a1b8932004-12-08 17:35:31 +0000[diff] [blame]421</p>
Misha Brukman773d6f62004-03-01 18:21:04 +0000[diff] [blame]422
Tanya Lattner9a1b8932004-12-08 17:35:31 +0000[diff] [blame]423<p>For example, to run the Regression tests, type
424<tt>gmake TESTSUITE=Regression</tt> in <tt>llvm/tests</tt>.</p>
Misha Brukman773d6f62004-03-01 18:21:04 +0000[diff] [blame]425
Reid Spencerae21b0b2004-09-05 20:07:26 +0000[diff] [blame]426<p>Note that there are no Makefiles in <tt>llvm/test/Features</tt> and
Tanya Lattner9a1b8932004-12-08 17:35:31 +0000[diff] [blame]427<tt>llvm/test/Regression</tt>. You must use DejaGNU from the <tt>llvm/test</tt>
Reid Spencerae21b0b2004-09-05 20:07:26 +0000[diff] [blame]428directory to run them.</p>
Misha Brukman773d6f62004-03-01 18:21:04 +0000[diff] [blame]429
Reid Spencerae21b0b2004-09-05 20:07:26 +0000[diff] [blame]430<p>To run the <tt>llvm-test</tt> suite, you need to use the following steps:
431</p>
432<ol>
433 <li>cd into the llvm/projects directory</li>
434 <li>check out the <tt>llvm-test</tt> module with:<br/>
Reid Spencerca058542006-03-14 05:39:39 +0000[diff] [blame]435 <tt>cvs -d :pserver:anon@llvm.org:/var/cvs/llvm co -PR llvm-test</tt><br>
Reid Spencerae21b0b2004-09-05 20:07:26 +0000[diff] [blame]436 This will get the test suite into <tt>llvm/projects/llvm-test</tt></li>
437 <li>configure the test suite. You can do this one of two ways:
438 <ol>
439 <li>Use the regular llvm configure:<br/>
440 <tt>cd $LLVM_OBJ_ROOT ; $LLVM_SRC_ROOT/configure</tt><br/>
441 This will ensure that the <tt>projects/llvm-test</tt> directory is also
442 properly configured.</li>
443 <li>Use the <tt>configure</tt> script found in the <tt>llvm-test</tt> source
444 directory:<br/>
Chris Lattner15f17ec2006-05-23 01:25:11 +0000[diff] [blame]445 <tt>$LLVM_SRC_ROOT/projects/llvm-test/configure
446 --with-llvmsrc=$LLVM_SRC_ROOT --with-llvmobj=$LLVM_OBJ_ROOT</tt>
Reid Spencerae21b0b2004-09-05 20:07:26 +0000[diff] [blame]447 </li>
448 </ol>
449 <li>gmake</li>
450</ol>
451<p>Note that the second and third steps only need to be done once. After you
452have the suite checked out and configured, you don't need to do it again (unless
453the test code or configure script changes).</p>
454
455<p>To make a specialized test (use one of the
456<tt>llvm-test/TEST.&lt;type&gt;.Makefile</tt>s), just run:<br/>
457<tt>gmake TEST=&lt;type&gt; test</tt><br/>For example, you could run the
Misha Brukman773d6f62004-03-01 18:21:04 +0000[diff] [blame]458nightly tester tests using the following commands:</p>
459
460<pre>
Reid Spencerae21b0b2004-09-05 20:07:26 +0000[diff] [blame]461 % cd llvm/projects/llvm-test
Misha Brukman773d6f62004-03-01 18:21:04 +0000[diff] [blame]462 % gmake TEST=nightly test
463</pre>
464
465<p>Regardless of which test you're running, the results are printed on standard
466output and standard error. You can redirect these results to a file if you
467choose.</p>
468
469<p>Some tests are known to fail. Some are bugs that we have not fixed yet;
Tanya Lattner9a1b8932004-12-08 17:35:31 +0000[diff] [blame]470others are features that we haven't added yet (or may never add). In DejaGNU,
Misha Brukman773d6f62004-03-01 18:21:04 +0000[diff] [blame]471the result for such tests will be XFAIL (eXpected FAILure). In this way, you
472can tell the difference between an expected and unexpected failure.</p>
473
John Criswell417cb0a2005-05-13 19:48:07 +0000[diff] [blame]474<p>The tests in <tt>llvm-test</tt> have no such feature at this time. If the
Misha Brukman8d08d362004-10-08 00:41:27 +0000[diff] [blame]475test passes, only warnings and other miscellaneous output will be generated. If
476a test fails, a large &lt;program&gt; FAILED message will be displayed. This
477will help you separate benign warnings from actual test failures.</p>
Chris Lattnerc4f22522004-06-24 20:53:09 +0000[diff] [blame]478
479</div>
480
Chris Lattner17d145e2006-05-23 01:40:20 +0000[diff] [blame]481<!-- _______________________________________________________________________ -->
482<div class="doc_subsection">
483<a name="customtest">Writing custom tests for llvm-test</a></div>
484<!-- _______________________________________________________________________ -->
485
486<div class="doc_text">
487
488<p>Assuming you can run llvm-test, (e.g. "<tt>gmake TEST=nightly report</tt>"
489should work), it is really easy to run optimizations or code generator
490components against every program in the tree, collecting statistics or running
491custom checks for correctness. At base, this is how the nightly tester works,
492it's just one example of a general framework.</p>
493
494<p>Lets say that you have an LLVM optimization pass, and you want to see how
495many times it triggers. First thing you should do is add an LLVM
496<a href="ProgrammersManual.html#Statistic">statistic</a> to your pass, which
497will tally counts of things you care about.</p>
498
499<p>Following this, you can set up a test and a report that collects these and
500formats them for easy viewing. This consists of two files, an
501"<tt>llvm-test/TEST.XXX.Makefile</tt>" fragment (where XXX is the name of your
502test) and an "<tt>llvm-test/TEST.XXX.report</tt>" file that indicates how to
503format the output into a table. There are many example reports of various
504levels of sophistication included with llvm-test, and the framework is very
505general.</p>
506
507<p>If you are interested in testing an optimization pass, check out the
508"libcalls" test as an example. It can be run like this:<p>
509
510<div class="doc_code">
511<pre>
512% cd llvm/projects/llvm-test/MultiSource/Benchmarks # or some other level
513% make TEST=libcalls report
514</pre>
515</div>
516
517<p>This will do a bunch of stuff, then eventually print a table like this:</p>
518
519<div class="doc_code">
520<pre>
521Name | total | #exit |
522...
523FreeBench/analyzer/analyzer | 51 | 6 |
524FreeBench/fourinarow/fourinarow | 1 | 1 |
525FreeBench/neural/neural | 19 | 9 |
526FreeBench/pifft/pifft | 5 | 3 |
527MallocBench/cfrac/cfrac | 1 | * |
528MallocBench/espresso/espresso | 52 | 12 |
529MallocBench/gs/gs | 4 | * |
530Prolangs-C/TimberWolfMC/timberwolfmc | 302 | * |
531Prolangs-C/agrep/agrep | 33 | 12 |
532Prolangs-C/allroots/allroots | * | * |
533Prolangs-C/assembler/assembler | 47 | * |
534Prolangs-C/bison/mybison | 74 | * |
535...
536</pre>
537</div>
538
539<p>This basically is grepping the -stats output and displaying it in a table.
540You can also use the "TEST=libcalls report.html" target to get the table in HTML
541form, similarly for report.csv and report.tex.</p>
542
543<p>The source for this is in llvm-test/TEST.libcalls.*. The format is pretty
544simple: the Makefile indicates how to run the test (in this case,
545"<tt>opt -simplify-libcalls -stats</tt>"), and the report contains one line for
546each column of the output. The first value is the header for the column and the
547second is the regex to grep the output of the command for. There are lots of
548example reports that can do fancy stuff.</p>
549
550</div>
551
552
Reid Spencerae21b0b2004-09-05 20:07:26 +0000[diff] [blame]553<!--=========================================================================-->
Chris Lattnerc4f22522004-06-24 20:53:09 +0000[diff] [blame]554<div class="doc_section"><a name="nightly">Running the nightly tester</a></div>
Reid Spencerae21b0b2004-09-05 20:07:26 +0000[diff] [blame]555<!--=========================================================================-->
Chris Lattnerc4f22522004-06-24 20:53:09 +0000[diff] [blame]556
557<div class="doc_text">
558
559<p>
Patrick Jenkins04ed1422006-08-11 23:27:02 +0000[diff] [blame^]560The <a href="http://llvm.org/nightlytest/">LLVM Nightly Testers</a>
Chris Lattnerc4f22522004-06-24 20:53:09 +0000[diff] [blame]561automatically check out an LLVM tree, build it, run the "nightly"
Patrick Jenkins04ed1422006-08-11 23:27:02 +0000[diff] [blame^]562program test (described above), run all of the feature and regression tests,
563delete the checked out tree, and then submit the results to
564<a href="http://llvm.org/nightlytest/">http://llvm.org/nightlytest/</a>.
565After test results are submitted to
566<a href="http://llvm.org/nightlytest/">http://llvm.org/nightlytest/</a>,
567they are processed and displayed on the tests page. An email to
568<a href="http://lists.cs.uiuc.edu/pipermail/llvm-testresults/">
569llvm-testresults@cs.uiuc.edu</a> summarizing the results is also generated.
570This testing scheme is designed to ensure that programs don't break as well
571as keep track of LLVM's progress over time.</p>
Chris Lattnerc4f22522004-06-24 20:53:09 +0000[diff] [blame]572
Patrick Jenkins04ed1422006-08-11 23:27:02 +0000[diff] [blame^]573<p>If you'd like to set up an instance of the nightly tester to run on your
574machine, take a look at the comments at the top of the
575<tt>utils/NewNightlyTest.pl</tt> file. If you decide to set up a nightly tester
576please choose a unique nickname and invoke <tt>utils/NewNightlyTest.pl</tt>
577with the "-nickname [yournickname]" command line option. We usually run it
578from a crontab entry that looks like this:</p>
Chris Lattnerc4f22522004-06-24 20:53:09 +0000[diff] [blame]579
Misha Brukman5da60ba2005-03-10 22:51:59 +0000[diff] [blame]580<div class="doc_code">
Chris Lattnerc4f22522004-06-24 20:53:09 +0000[diff] [blame]581<pre>
Patrick Jenkins04ed1422006-08-11 23:27:02 +0000[diff] [blame^]5825 3 * * * $HOME/llvm/utils/NewNightlyTest.pl -parallel -nickname Nickname \
583 $CVSROOT $HOME/buildtest $HOME/cvs/testresults
Chris Lattnerc4f22522004-06-24 20:53:09 +0000[diff] [blame]584</pre>
Misha Brukman5da60ba2005-03-10 22:51:59 +0000[diff] [blame]585</div>
Chris Lattnerc4f22522004-06-24 20:53:09 +0000[diff] [blame]586
Reid Spencerae21b0b2004-09-05 20:07:26 +0000[diff] [blame]587<p>Or, you can create a shell script to encapsulate the running of the script.
Misha Brukman5da60ba2005-03-10 22:51:59 +0000[diff] [blame]588The optimized x86 Linux nightly test is run from just such a script:</p>
589
590<div class="doc_code">
Reid Spencerae21b0b2004-09-05 20:07:26 +0000[diff] [blame]591<pre>
592#!/bin/bash
593BASE=/proj/work/llvm/nightlytest
Reid Spencerca058542006-03-14 05:39:39 +0000[diff] [blame]594export CVSROOT=:pserver:anon@llvm.org:/var/cvs/llvm
Reid Spencerae21b0b2004-09-05 20:07:26 +0000[diff] [blame]595export BUILDDIR=$BASE/build
596export WEBDIR=$BASE/testresults
597export LLVMGCCDIR=/proj/work/llvm/cfrontend/install
598export PATH=/proj/install/bin:$LLVMGCCDIR/bin:$PATH
599export LD_LIBRARY_PATH=/proj/install/lib
Reid Spencerae21b0b2004-09-05 20:07:26 +0000[diff] [blame]600cd $BASE
Patrick Jenkins04ed1422006-08-11 23:27:02 +0000[diff] [blame^]601cp /proj/work/llvm/llvm/utils/NewNightlyTest.pl .
602nice ./NewNightlyTest.pl -nice -release -verbose -parallel -enable-linscan \
603 -nickname NightlyTester -noexternals 2&gt;&amp;1 &gt; output.log
Reid Spencerae21b0b2004-09-05 20:07:26 +0000[diff] [blame]604</pre>
Misha Brukman5da60ba2005-03-10 22:51:59 +0000[diff] [blame]605</div>
Reid Spencerae21b0b2004-09-05 20:07:26 +0000[diff] [blame]606
Patrick Jenkins04ed1422006-08-11 23:27:02 +0000[diff] [blame^]607<p>It is also possible to specify the the location your nightly test results
608are submitted. You can do this by passing the command line option
609"-submit-server [server_address]" and "-submit-script [script_on_server]" to
610<tt>utils/NewNightlyTest.pl</tt>. For example, to submit to the llvm.org
611nightly test results page, you would invoke the nightly test script with
612"-submit-server llvm.org -submit-script /nightlytest/NightlyTestAccept.cgi".
613If these options are not specified, the nightly test script sends the results
614to the llvm.org nightly test results page.</p>
615
616<p>Take a look at the <tt>NewNightlyTest.pl</tt> file to see what all of the
617flags and strings do. If you start running the nightly tests, please let us
618know. Thanks!</p>
Misha Brukman5da60ba2005-03-10 22:51:59 +0000[diff] [blame]619
Misha Brukman773d6f62004-03-01 18:21:04 +0000[diff] [blame]620</div>
John Criswelle90fc1f2003-10-10 18:42:49 +0000[diff] [blame]621
Brian Gaeke739811d2003-10-23 18:10:28 +0000[diff] [blame]622<!-- *********************************************************************** -->
John Criswelle90fc1f2003-10-10 18:42:49 +0000[diff] [blame]623
Misha Brukman773d6f62004-03-01 18:21:04 +0000[diff] [blame]624<hr>
625<address>
626 <a href="http://jigsaw.w3.org/css-validator/check/referer"><img
627 src="http://jigsaw.w3.org/css-validator/images/vcss" alt="Valid CSS!"></a>
628 <a href="http://validator.w3.org/check/referer"><img
629 src="http://www.w3.org/Icons/valid-html401" alt="Valid HTML 4.01!" /></a>
Brian Gaeke739811d2003-10-23 18:10:28 +0000[diff] [blame]630
John Criswell417cb0a2005-05-13 19:48:07 +0000[diff] [blame]631 John T. Criswell, Reid Spencer, and Tanya Lattner<br>
Reid Spencerca058542006-03-14 05:39:39 +0000[diff] [blame]632 <a href="http://llvm.org">The LLVM Compiler Infrastructure</a><br/>
Misha Brukman773d6f62004-03-01 18:21:04 +0000[diff] [blame]633 Last modified: $Date$
634</address>
Brian Gaeke739811d2003-10-23 18:10:28 +0000[diff] [blame]635</body>
John Criswelle90fc1f2003-10-10 18:42:49 +0000[diff] [blame]636</html>