Gitiles
Code Review Sign In
gerrit-public.fairphone.software / toolchain / llvm-project / b8004d9b4c34a6d19be4ec658e331239b55c2f93 / . / llvm / docs / TestingGuide.html
blob: 3309ac3b33cf672049ae264d0680a0c1a90b80cd [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>
NAKAMURA Takumib8004d92011-10-31 11:21:59 +0000[diff] [blame^]5 <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
Matthijs Kooijman8fd28412008-06-24 12:58:31 +0000[diff] [blame]6 <title>LLVM Testing Infrastructure Guide</title>
Misha Brukman773d6f62004-03-01 18:21:04 +0000[diff] [blame]7 <link rel="stylesheet" href="llvm.css" type="text/css">
Brian Gaeke739811d2003-10-23 18:10:28 +0000[diff] [blame]8</head>
Brian Gaeke739811d2003-10-23 18:10:28 +0000[diff] [blame]9<body>
10
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000[diff] [blame]11<h1>
Matthijs Kooijman8fd28412008-06-24 12:58:31 +0000[diff] [blame]12 LLVM Testing Infrastructure Guide
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000[diff] [blame]13</h1>
John Criswelle90fc1f2003-10-10 18:42:49 +0000[diff] [blame]14
Brian Gaeke739811d2003-10-23 18:10:28 +0000[diff] [blame]15<ol>
Reid Spencer49fb40c2004-11-01 08:30:14 +0000[diff] [blame]16 <li><a href="#overview">Overview</a></li>
Matthijs Kooijman8fd28412008-06-24 12:58:31 +0000[diff] [blame]17 <li><a href="#requirements">Requirements</a></li>
18 <li><a href="#org">LLVM testing infrastructure organization</a>
Reid Spencer49fb40c2004-11-01 08:30:14 +0000[diff] [blame]19 <ul>
Daniel Dunbarf85eb932010-08-02 01:20:23 +0000[diff] [blame]20 <li><a href="#regressiontests">Regression tests</a></li>
Matthijs Kooijman8fd28412008-06-24 12:58:31 +0000[diff] [blame]21 <li><a href="#testsuite">Test suite</a></li>
Devang Patelfd0ad362010-11-11 00:13:39 +0000[diff] [blame]22 <li><a href="#debuginfotests">Debugging Information tests</a></li>
Reid Spencer49fb40c2004-11-01 08:30:14 +0000[diff] [blame]23 </ul>
24 </li>
Matthijs Kooijman8fd28412008-06-24 12:58:31 +0000[diff] [blame]25 <li><a href="#quick">Quick start</a>
Chris Lattner17d145e2006-05-23 01:40:20 +0000[diff] [blame]26 <ul>
Daniel Dunbarf85eb932010-08-02 01:20:23 +0000[diff] [blame]27 <li><a href="#quickregressiontests">Regression tests</a></li>
Matthijs Kooijman8fd28412008-06-24 12:58:31 +0000[diff] [blame]28 <li><a href="#quicktestsuite">Test suite</a></li>
Devang Patelfd0ad362010-11-11 00:13:39 +0000[diff] [blame]29 <li><a href="#quickdebuginfotests">Debugging Information tests</a></li>
Matthijs Kooijmane7d45b12008-05-23 11:45:18 +0000[diff] [blame]30 </ul>
31 </li>
Daniel Dunbarf85eb932010-08-02 01:20:23 +0000[diff] [blame]32 <li><a href="#rtstructure">Regression test structure</a>
Matthijs Kooijmane7d45b12008-05-23 11:45:18 +0000[diff] [blame]33 <ul>
Daniel Dunbarf85eb932010-08-02 01:20:23 +0000[diff] [blame]34 <li><a href="#rtcustom">Writing new regression tests</a></li>
Chris Lattner7e11b722009-08-15 15:40:48 +0000[diff] [blame]35 <li><a href="#FileCheck">The FileCheck utility</a></li>
Daniel Dunbarf85eb932010-08-02 01:20:23 +0000[diff] [blame]36 <li><a href="#rtvars">Variables and substitutions</a></li>
37 <li><a href="#rtfeatures">Other features</a></li>
Matthijs Kooijmane7d45b12008-05-23 11:45:18 +0000[diff] [blame]38 </ul>
39 </li>
Matthijs Kooijman8fd28412008-06-24 12:58:31 +0000[diff] [blame]40 <li><a href="#testsuitestructure">Test suite structure</a></li>
41 <li><a href="#testsuiterun">Running the test suite</a>
Matthijs Kooijmane7d45b12008-05-23 11:45:18 +0000[diff] [blame]42 <ul>
Stuart Hastings6d437692009-05-21 20:23:59 +0000[diff] [blame]43 <li><a href="#testsuiteexternal">Configuring External Tests</a></li>
Matthijs Kooijman8fd28412008-06-24 12:58:31 +0000[diff] [blame]44 <li><a href="#testsuitetests">Running different tests</a></li>
45 <li><a href="#testsuiteoutput">Generating test output</a></li>
Andrew Trick68aa18e42010-09-23 20:26:44 +0000[diff] [blame]46 <li><a href="#testsuitecustom">Writing custom tests for test-suite</a></li>
Matthijs Kooijmane7d45b12008-05-23 11:45:18 +0000[diff] [blame]47 </ul>
Chris Lattner17d145e2006-05-23 01:40:20 +0000[diff] [blame]48 </li>
Brian Gaeke739811d2003-10-23 18:10:28 +0000[diff] [blame]49</ol>
John Criswelle90fc1f2003-10-10 18:42:49 +0000[diff] [blame]50
Chris Lattner020e1fc2004-05-23 21:07:27 +0000[diff] [blame]51<div class="doc_author">
Daniel Dunbarf85eb932010-08-02 01:20:23 +0000[diff] [blame]52 <p>Written by John T. Criswell, Daniel Dunbar, Reid Spencer, and Tanya Lattner</p>
Chris Lattner020e1fc2004-05-23 21:07:27 +0000[diff] [blame]53</div>
John Criswelle90fc1f2003-10-10 18:42:49 +0000[diff] [blame]54
Reid Spencerae21b0b2004-09-05 20:07:26 +0000[diff] [blame]55<!--=========================================================================-->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000[diff] [blame]56<h2><a name="overview">Overview</a></h2>
Reid Spencerae21b0b2004-09-05 20:07:26 +0000[diff] [blame]57<!--=========================================================================-->
John Criswelle90fc1f2003-10-10 18:42:49 +0000[diff] [blame]58
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000[diff] [blame]59<div>
John Criswelle90fc1f2003-10-10 18:42:49 +0000[diff] [blame]60
Daniel Dunbarf85eb932010-08-02 01:20:23 +0000[diff] [blame]61<p>This document is the reference manual for the LLVM testing infrastructure. It
62documents the structure of the LLVM testing infrastructure, the tools needed to
63use it, and how to add and run tests.</p>
John Criswelle90fc1f2003-10-10 18:42:49 +0000[diff] [blame]64
Misha Brukman773d6f62004-03-01 18:21:04 +0000[diff] [blame]65</div>
John Criswelle90fc1f2003-10-10 18:42:49 +0000[diff] [blame]66
Reid Spencerae21b0b2004-09-05 20:07:26 +0000[diff] [blame]67<!--=========================================================================-->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000[diff] [blame]68<h2><a name="requirements">Requirements</a></h2>
Reid Spencerae21b0b2004-09-05 20:07:26 +0000[diff] [blame]69<!--=========================================================================-->
John Criswelle90fc1f2003-10-10 18:42:49 +0000[diff] [blame]70
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000[diff] [blame]71<div>
John Criswelle90fc1f2003-10-10 18:42:49 +0000[diff] [blame]72
Daniel Dunbarf85eb932010-08-02 01:20:23 +0000[diff] [blame]73<p>In order to use the LLVM testing infrastructure, you will need all of the
74software required to build LLVM, as well
75as <a href="http://python.org">Python</a> 2.4 or later.</p>
Jim Laskey27abf2b2006-03-27 18:41:06 +0000[diff] [blame]76
Misha Brukman773d6f62004-03-01 18:21:04 +0000[diff] [blame]77</div>
John Criswelle90fc1f2003-10-10 18:42:49 +0000[diff] [blame]78
Reid Spencerae21b0b2004-09-05 20:07:26 +0000[diff] [blame]79<!--=========================================================================-->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000[diff] [blame]80<h2><a name="org">LLVM testing infrastructure organization</a></h2>
Matthijs Kooijmane7d45b12008-05-23 11:45:18 +0000[diff] [blame]81<!--=========================================================================-->
82
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000[diff] [blame]83<div>
Matthijs Kooijmane7d45b12008-05-23 11:45:18 +0000[diff] [blame]84
Daniel Dunbarf85eb932010-08-02 01:20:23 +0000[diff] [blame]85<p>The LLVM testing infrastructure contains two major categories of tests:
86regression tests and whole programs. The regression tests are contained inside
87the LLVM repository itself under <tt>llvm/test</tt> and are expected to always
88pass -- they should be run before every commit. The whole programs tests are
89referred to as the "LLVM test suite" and are in the <tt>test-suite</tt> module
90in subversion.
Matthijs Kooijman8fd28412008-06-24 12:58:31 +0000[diff] [blame]91</p>
Matthijs Kooijmane7d45b12008-05-23 11:45:18 +0000[diff] [blame]92
Matthijs Kooijmane7d45b12008-05-23 11:45:18 +0000[diff] [blame]93<!-- _______________________________________________________________________ -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000[diff] [blame]94<h3><a name="regressiontests">Regression tests</a></h3>
Matthijs Kooijmane7d45b12008-05-23 11:45:18 +0000[diff] [blame]95<!-- _______________________________________________________________________ -->
96
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000[diff] [blame]97<div>
Matthijs Kooijmane7d45b12008-05-23 11:45:18 +0000[diff] [blame]98
Daniel Dunbarf85eb932010-08-02 01:20:23 +0000[diff] [blame]99<p>The regression tests are small pieces of code that test a specific feature of
100LLVM or trigger a specific bug in LLVM. They are usually written in LLVM
101assembly language, but can be written in other languages if the test targets a
102particular language front end (and the appropriate <tt>--with-llvmgcc</tt>
103options were used at <tt>configure</tt> time of the <tt>llvm</tt> module). These
104tests are driven by the 'lit' testing tool, which is part of LLVM.</p>
Matthijs Kooijmane7d45b12008-05-23 11:45:18 +0000[diff] [blame]105
Shantonu Sen89d5c412009-06-26 05:44:53 +0000[diff] [blame]106<p>These code fragments are not complete programs. The code generated
107from them is never executed to determine correct behavior.</p>
Matthijs Kooijmane7d45b12008-05-23 11:45:18 +0000[diff] [blame]108
109<p>These code fragment tests are located in the <tt>llvm/test</tt>
110directory.</p>
111
112<p>Typically when a bug is found in LLVM, a regression test containing
113just enough code to reproduce the problem should be written and placed
114somewhere underneath this directory. In most cases, this will be a small
115piece of LLVM assembly language code, often distilled from an actual
116application or benchmark.</p>
117
118</div>
119
120<!-- _______________________________________________________________________ -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000[diff] [blame]121<h3><a name="testsuite">Test suite</a></h3>
Matthijs Kooijmane7d45b12008-05-23 11:45:18 +0000[diff] [blame]122<!-- _______________________________________________________________________ -->
123
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000[diff] [blame]124<div>
Matthijs Kooijmane7d45b12008-05-23 11:45:18 +0000[diff] [blame]125
Matthijs Kooijman8fd28412008-06-24 12:58:31 +0000[diff] [blame]126<p>The test suite contains whole programs, which are pieces of
Matthijs Kooijmane7d45b12008-05-23 11:45:18 +0000[diff] [blame]127code which can be compiled and linked into a stand-alone program that can be
128executed. These programs are generally written in high level languages such as
129C or C++, but sometimes they are written straight in LLVM assembly.</p>
130
131<p>These programs are compiled and then executed using several different
132methods (native compiler, LLVM C backend, LLVM JIT, LLVM native code generation,
133etc). The output of these programs is compared to ensure that LLVM is compiling
134the program correctly.</p>
135
136<p>In addition to compiling and executing programs, whole program tests serve as
137a way of benchmarking LLVM performance, both in terms of the efficiency of the
138programs generated as well as the speed with which LLVM compiles, optimizes, and
139generates code.</p>
140
Matthijs Kooijman8fd28412008-06-24 12:58:31 +0000[diff] [blame]141<p>The test-suite is located in the <tt>test-suite</tt> Subversion module.</p>
Matthijs Kooijmane7d45b12008-05-23 11:45:18 +0000[diff] [blame]142
143</div>
144
Devang Patelfd0ad362010-11-11 00:13:39 +0000[diff] [blame]145<!-- _______________________________________________________________________ -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000[diff] [blame]146<h3><a name="debuginfotests">Debugging Information tests</a></h3>
Devang Patelfd0ad362010-11-11 00:13:39 +0000[diff] [blame]147<!-- _______________________________________________________________________ -->
148
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000[diff] [blame]149<div>
Devang Patelfd0ad362010-11-11 00:13:39 +0000[diff] [blame]150
151<p>The test suite contains tests to check quality of debugging information.
152The test are written in C based languages or in LLVM assembly language. </p>
153
154<p>These tests are compiled and run under a debugger. The debugger output
155is checked to validate of debugging information. See README.txt in the
156test suite for more information . This test suite is located in the
157<tt>debuginfo-tests</tt> Subversion module. </p>
158
159</div>
160
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000[diff] [blame]161</div>
162
Matthijs Kooijmane7d45b12008-05-23 11:45:18 +0000[diff] [blame]163<!--=========================================================================-->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000[diff] [blame]164<h2><a name="quick">Quick start</a></h2>
Reid Spencerae21b0b2004-09-05 20:07:26 +0000[diff] [blame]165<!--=========================================================================-->
John Criswelle90fc1f2003-10-10 18:42:49 +0000[diff] [blame]166
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000[diff] [blame]167<div>
Brian Gaeke739811d2003-10-23 18:10:28 +0000[diff] [blame]168
Daniel Dunbarf85eb932010-08-02 01:20:23 +0000[diff] [blame]169 <p>The tests are located in two separate Subversion modules. The regressions
170 tests are in the main "llvm" module under the directory
Matthijs Kooijmane7d45b12008-05-23 11:45:18 +0000[diff] [blame]171 <tt>llvm/test</tt> (so you get these tests for free with the main llvm tree).
Matthijs Kooijman8fd28412008-06-24 12:58:31 +0000[diff] [blame]172 The more comprehensive test suite that includes whole
173programs in C and C++ is in the <tt>test-suite</tt> module. This module should
174be checked out to the <tt>llvm/projects</tt> directory (don't use another name
Duncan Sands8eb254a2010-11-03 08:16:50 +0000[diff] [blame]175than the default "test-suite", for then the test suite will be run every time
Matthijs Kooijman8fd28412008-06-24 12:58:31 +0000[diff] [blame]176you run <tt>make</tt> in the main <tt>llvm</tt> directory).
Matthijs Kooijmane7d45b12008-05-23 11:45:18 +0000[diff] [blame]177When you <tt>configure</tt> the <tt>llvm</tt> module,
Matthijs Kooijman8fd28412008-06-24 12:58:31 +0000[diff] [blame]178the <tt>test-suite</tt> directory will be automatically configured.
Reid Spencerc7f87f22007-07-09 08:04:31 +0000[diff] [blame]179Alternatively, you can configure the <tt>test-suite</tt> module manually.</p>
Matthijs Kooijmane7d45b12008-05-23 11:45:18 +0000[diff] [blame]180
181<!-- _______________________________________________________________________ -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000[diff] [blame]182<h3><a name="quickregressiontests">Regression tests</a></h3>
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000[diff] [blame]183<div>
Matthijs Kooijmane7d45b12008-05-23 11:45:18 +0000[diff] [blame]184<!-- _______________________________________________________________________ -->
Daniel Dunbarf85eb932010-08-02 01:20:23 +0000[diff] [blame]185<p>To run all of the LLVM regression tests, use master Makefile in
186 the <tt>llvm/test</tt> directory:</p>
Bill Wendling6275c232007-09-22 09:16:44 +0000[diff] [blame]187
188<div class="doc_code">
Misha Brukman773d6f62004-03-01 18:21:04 +0000[diff] [blame]189<pre>
Reid Spencerae21b0b2004-09-05 20:07:26 +0000[diff] [blame]190% gmake -C llvm/test
Misha Brukman773d6f62004-03-01 18:21:04 +0000[diff] [blame]191</pre>
Bill Wendling6275c232007-09-22 09:16:44 +0000[diff] [blame]192</div>
193
194<p>or</p>
195
196<div class="doc_code">
Tanya Lattner4d690182004-12-06 02:11:52 +0000[diff] [blame]197<pre>
198% gmake check
199</pre>
Bill Wendling6275c232007-09-22 09:16:44 +0000[diff] [blame]200</div>
John Criswell61617f72005-05-13 20:25:49 +0000[diff] [blame]201
NAKAMURA Takumica46f5a2011-04-09 02:13:37 +0000[diff] [blame]202<p>If you have <a href="http://clang.llvm.org/">Clang</a> checked out and built,
Daniel Dunbarf85eb932010-08-02 01:20:23 +0000[diff] [blame]203you can run the LLVM and Clang tests simultaneously using:</p>
204
205<p>or</p>
Bill Wendling6275c232007-09-22 09:16:44 +0000[diff] [blame]206
207<div class="doc_code">
Tanya Lattner4d690182004-12-06 02:11:52 +0000[diff] [blame]208<pre>
Daniel Dunbarf85eb932010-08-02 01:20:23 +0000[diff] [blame]209% gmake check-all
Matthijs Kooijmane7d45b12008-05-23 11:45:18 +0000[diff] [blame]210</pre>
211</div>
212
Nuno Lopesab6d6072008-11-25 15:57:52 +0000[diff] [blame]213<p>To run the tests with Valgrind (Memcheck by default), just append
214<tt>VG=1</tt> to the commands above, e.g.:</p>
215
216<div class="doc_code">
217<pre>
218% gmake check VG=1
219</pre>
220</div>
221
Daniel Dunbarf85eb932010-08-02 01:20:23 +0000[diff] [blame]222<p>To run individual tests or subsets of tests, you can use the 'llvm-lit'
223script which is built as part of LLVM. For example, to run the
224'Integer/BitCast.ll' test by itself you can run:</p>
225
226<div class="doc_code">
227<pre>
228% llvm-lit ~/llvm/test/Integer/BitCast.ll
229</pre>
230</div>
231
232<p>or to run all of the ARM CodeGen tests:</p>
233
234<div class="doc_code">
235<pre>
236% llvm-lit ~/llvm/test/CodeGen/ARM
237</pre>
238</div>
239
240<p>For more information on using the 'lit' tool, see 'llvm-lit --help' or the
241'lit' man page.</p>
242
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000[diff] [blame]243</div>
244
Matthijs Kooijmane7d45b12008-05-23 11:45:18 +0000[diff] [blame]245<!-- _______________________________________________________________________ -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000[diff] [blame]246<h3><a name="quicktestsuite">Test suite</a></h3>
Matthijs Kooijmane7d45b12008-05-23 11:45:18 +0000[diff] [blame]247<!-- _______________________________________________________________________ -->
248
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000[diff] [blame]249<div>
250
Reid Spencerae21b0b2004-09-05 20:07:26 +0000[diff] [blame]251<p>To run the comprehensive test suite (tests that compile and execute whole
Matthijs Kooijmane7d45b12008-05-23 11:45:18 +0000[diff] [blame]252programs), first checkout and setup the <tt>test-suite</tt> module:</p>
John Criswelle90fc1f2003-10-10 18:42:49 +0000[diff] [blame]253
Bill Wendling6275c232007-09-22 09:16:44 +0000[diff] [blame]254<div class="doc_code">
Misha Brukman773d6f62004-03-01 18:21:04 +0000[diff] [blame]255<pre>
Reid Spencerae21b0b2004-09-05 20:07:26 +0000[diff] [blame]256% cd llvm/projects
Matthijs Kooijman8fd28412008-06-24 12:58:31 +0000[diff] [blame]257% svn co http://llvm.org/svn/llvm-project/test-suite/trunk test-suite
Tanya Lattner84603742007-11-28 05:13:45 +0000[diff] [blame]258% cd ..
259% ./configure --with-llvmgccdir=$LLVM_GCC_DIR
Misha Brukman773d6f62004-03-01 18:21:04 +0000[diff] [blame]260</pre>
Bill Wendling6275c232007-09-22 09:16:44 +0000[diff] [blame]261</div>
Misha Brukman773d6f62004-03-01 18:21:04 +0000[diff] [blame]262
Shantonu Sen89d5c412009-06-26 05:44:53 +0000[diff] [blame]263<p>where <tt>$LLVM_GCC_DIR</tt> is the directory where
Chris Lattner3e6c9192010-11-03 00:30:29 +0000[diff] [blame]264you <em>installed</em> llvm-gcc, not its src or obj
Shantonu Sen89d5c412009-06-26 05:44:53 +0000[diff] [blame]265dir. The <tt>--with-llvmgccdir</tt> option assumes that
266the <tt>llvm-gcc-4.2</tt> module was configured with
267<tt>--program-prefix=llvm-</tt>, and therefore that the C and C++
268compiler drivers are called <tt>llvm-gcc</tt> and <tt>llvm-g++</tt>
269respectively. If this is not the case,
270use <tt>--with-llvmgcc</tt>/<tt>--with-llvmgxx</tt> to specify each
271executable's location.</p>
272
Matthijs Kooijman8fd28412008-06-24 12:58:31 +0000[diff] [blame]273<p>Then, run the entire test suite by running make in the <tt>test-suite</tt>
Matthijs Kooijmane7d45b12008-05-23 11:45:18 +0000[diff] [blame]274directory:</p>
275
276<div class="doc_code">
277<pre>
Matthijs Kooijman8fd28412008-06-24 12:58:31 +0000[diff] [blame]278% cd projects/test-suite
Matthijs Kooijmane7d45b12008-05-23 11:45:18 +0000[diff] [blame]279% gmake
280</pre>
Misha Brukman773d6f62004-03-01 18:21:04 +0000[diff] [blame]281</div>
282
Matthijs Kooijmane7d45b12008-05-23 11:45:18 +0000[diff] [blame]283<p>Usually, running the "nightly" set of tests is a good idea, and you can also
284let it generate a report by running:</p>
Misha Brukman773d6f62004-03-01 18:21:04 +0000[diff] [blame]285
Matthijs Kooijmane7d45b12008-05-23 11:45:18 +0000[diff] [blame]286<div class="doc_code">
287<pre>
Matthijs Kooijman8fd28412008-06-24 12:58:31 +0000[diff] [blame]288% cd projects/test-suite
Matthijs Kooijmane7d45b12008-05-23 11:45:18 +0000[diff] [blame]289% gmake TEST=nightly report report.html
290</pre>
Misha Brukman773d6f62004-03-01 18:21:04 +0000[diff] [blame]291</div>
292
Matthijs Kooijmane7d45b12008-05-23 11:45:18 +0000[diff] [blame]293<p>Any of the above commands can also be run in a subdirectory of
Matthijs Kooijman8fd28412008-06-24 12:58:31 +0000[diff] [blame]294<tt>projects/test-suite</tt> to run the specified test only on the programs in
Matthijs Kooijmane7d45b12008-05-23 11:45:18 +0000[diff] [blame]295that subdirectory.</p>
Misha Brukman773d6f62004-03-01 18:21:04 +0000[diff] [blame]296
297</div>
298
Devang Patelfd0ad362010-11-11 00:13:39 +0000[diff] [blame]299<!-- _______________________________________________________________________ -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000[diff] [blame]300<h3><a name="quickdebuginfotests">Debugging Information tests</a></h3>
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000[diff] [blame]301<div>
Devang Patelfd0ad362010-11-11 00:13:39 +0000[diff] [blame]302<!-- _______________________________________________________________________ -->
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000[diff] [blame]303<div>
Devang Patelfd0ad362010-11-11 00:13:39 +0000[diff] [blame]304
305<p> To run debugging information tests simply checkout the tests inside
306clang/test directory. </p>
307
308<div class="doc_code">
309<pre>
310%cd clang/test
311% svn co http://llvm.org/svn/llvm-project/debuginfo-tests/trunk debuginfo-tests
312</pre>
313</div>
314
315<p> These tests are already set up to run as part of clang regression tests.</p>
316
317</div>
318
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000[diff] [blame]319</div>
320
321</div>
322
Reid Spencerae21b0b2004-09-05 20:07:26 +0000[diff] [blame]323<!--=========================================================================-->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000[diff] [blame]324<h2><a name="rtstructure">Regression test structure</a></h2>
Reid Spencerae21b0b2004-09-05 20:07:26 +0000[diff] [blame]325<!--=========================================================================-->
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000[diff] [blame]326<div>
Daniel Dunbarf85eb932010-08-02 01:20:23 +0000[diff] [blame]327 <p>The LLVM regression tests are driven by 'lit' and are located in
328 the <tt>llvm/test</tt> directory.
Misha Brukman773d6f62004-03-01 18:21:04 +0000[diff] [blame]329
Reid Spencer26e1f922007-02-08 17:00:55 +0000[diff] [blame]330 <p>This directory contains a large array of small tests
331 that exercise various features of LLVM and to ensure that regressions do not
332 occur. The directory is broken into several sub-directories, each focused on
Bill Wendling6637c572007-09-22 09:20:07 +0000[diff] [blame]333 a particular area of LLVM. A few of the important ones are:</p>
Matthijs Kooijmane7d45b12008-05-23 11:45:18 +0000[diff] [blame]334
Bill Wendling6637c572007-09-22 09:20:07 +0000[diff] [blame]335 <ul>
Reid Spencer26e1f922007-02-08 17:00:55 +0000[diff] [blame]336 <li><tt>Analysis</tt>: checks Analysis passes.</li>
337 <li><tt>Archive</tt>: checks the Archive library.</li>
338 <li><tt>Assembler</tt>: checks Assembly reader/writer functionality.</li>
Gabor Greifa54634a2007-07-06 22:07:22 +0000[diff] [blame]339 <li><tt>Bitcode</tt>: checks Bitcode reader/writer functionality.</li>
Reid Spencer26e1f922007-02-08 17:00:55 +0000[diff] [blame]340 <li><tt>CodeGen</tt>: checks code generation and each target.</li>
341 <li><tt>Features</tt>: checks various features of the LLVM language.</li>
Gabor Greifa54634a2007-07-06 22:07:22 +0000[diff] [blame]342 <li><tt>Linker</tt>: tests bitcode linking.</li>
Reid Spencer26e1f922007-02-08 17:00:55 +0000[diff] [blame]343 <li><tt>Transforms</tt>: tests each of the scalar, IPO, and utility
344 transforms to ensure they make the right transformations.</li>
345 <li><tt>Verifier</tt>: tests the IR verifier.</li>
Bill Wendling6637c572007-09-22 09:20:07 +0000[diff] [blame]346 </ul>
Brian Gaeke739811d2003-10-23 18:10:28 +0000[diff] [blame]347
Matthijs Kooijmane7d45b12008-05-23 11:45:18 +0000[diff] [blame]348<!-- _______________________________________________________________________ -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000[diff] [blame]349<h3><a name="rtcustom">Writing new regression tests</a></h3>
Matthijs Kooijmane7d45b12008-05-23 11:45:18 +0000[diff] [blame]350<!-- _______________________________________________________________________ -->
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000[diff] [blame]351<div>
Daniel Dunbarf85eb932010-08-02 01:20:23 +0000[diff] [blame]352 <p>The regression test structure is very simple, but does require some
353 information to be set. This information is gathered via <tt>configure</tt> and
354 is written to a file, <tt>lit.site.cfg</tt>
355 in <tt>llvm/test</tt>. The <tt>llvm/test</tt> Makefile does this work for
356 you.</p>
Tanya Lattner4d690182004-12-06 02:11:52 +0000[diff] [blame]357
Daniel Dunbarf85eb932010-08-02 01:20:23 +0000[diff] [blame]358 <p>In order for the regression tests to work, each directory of tests must
359 have a <tt>dg.exp</tt> file. Lit looks for this file to determine how to
360 run the tests. This file is just a Tcl script and it can do anything you want,
361 but we've standardized it for the LLVM regression tests. If you're adding a
Matthijs Kooijmane7d45b12008-05-23 11:45:18 +0000[diff] [blame]362 directory of tests, just copy <tt>dg.exp</tt> from another directory to get
Daniel Dunbarf85eb932010-08-02 01:20:23 +0000[diff] [blame]363 running. The standard <tt>dg.exp</tt> simply loads a Tcl library
364 (<tt>test/lib/llvm.exp</tt>) and calls the <tt>llvm_runtests</tt> function
365 defined in that library with a list of file names to run. The names are
366 obtained by using Tcl's glob command. Any directory that contains only
Reid Spencer9dcf4c22007-04-14 21:46:15 +0000[diff] [blame]367 directories does not need the <tt>dg.exp</tt> file.</p>
Tanya Lattner4d690182004-12-06 02:11:52 +0000[diff] [blame]368
Chad Rosier38fb5bb2011-05-18 18:07:16 +0000[diff] [blame]369 <p>The <tt>llvm-runtests</tt> function looks at each file that is passed to
370 it and gathers any lines together that match "RUN:". These are the "RUN" lines
Reid Spencer9dcf4c22007-04-14 21:46:15 +0000[diff] [blame]371 that specify how the test is to be run. So, each test script must contain
372 RUN lines if it is to do anything. If there are no RUN lines, the
373 <tt>llvm-runtests</tt> function will issue an error and the test will
374 fail.</p>
Misha Brukman5da60ba2005-03-10 22:51:59 +0000[diff] [blame]375
Reid Spencer9dcf4c22007-04-14 21:46:15 +0000[diff] [blame]376 <p>RUN lines are specified in the comments of the test program using the
377 keyword <tt>RUN</tt> followed by a colon, and lastly the command (pipeline)
378 to execute. Together, these lines form the "script" that
379 <tt>llvm-runtests</tt> executes to run the test case. The syntax of the
380 RUN lines is similar to a shell's syntax for pipelines including I/O
381 redirection and variable substitution. However, even though these lines
382 may <i>look</i> like a shell script, they are not. RUN lines are interpreted
383 directly by the Tcl <tt>exec</tt> command. They are never executed by a
384 shell. Consequently the syntax differs from normal shell script syntax in a
385 few ways. You can specify as many RUN lines as needed.</p>
Tanya Lattner4d690182004-12-06 02:11:52 +0000[diff] [blame]386
David Greenedc276c32011-01-03 17:30:25 +0000[diff] [blame]387 <p>lit performs substitution on each RUN line to replace LLVM tool
388 names with the full paths to the executable built for each tool (in
389 $(LLVM_OBJ_ROOT)/$(BuildMode)/bin). This ensures that lit does not
390 invoke any stray LLVM tools in the user's path during testing.</p>
391
Reid Spencer9dcf4c22007-04-14 21:46:15 +0000[diff] [blame]392 <p>Each RUN line is executed on its own, distinct from other lines unless
393 its last character is <tt>\</tt>. This continuation character causes the RUN
394 line to be concatenated with the next one. In this way you can build up long
395 pipelines of commands without making huge line lengths. The lines ending in
396 <tt>\</tt> are concatenated until a RUN line that doesn't end in <tt>\</tt> is
Matthijs Kooijmane7d45b12008-05-23 11:45:18 +0000[diff] [blame]397 found. This concatenated set of RUN lines then constitutes one execution.
Reid Spencer9dcf4c22007-04-14 21:46:15 +0000[diff] [blame]398 Tcl will substitute variables and arrange for the pipeline to be executed. If
399 any process in the pipeline fails, the entire line (and test case) fails too.
400 </p>
Tanya Lattner4d690182004-12-06 02:11:52 +0000[diff] [blame]401
Reid Spencere2965482007-04-15 08:01:04 +0000[diff] [blame]402 <p> Below is an example of legal RUN lines in a <tt>.ll</tt> file:</p>
Bill Wendling6275c232007-09-22 09:16:44 +0000[diff] [blame]403
404<div class="doc_code">
405<pre>
406; RUN: llvm-as &lt; %s | llvm-dis &gt; %t1
407; RUN: llvm-dis &lt; %s.bc-13 &gt; %t2
408; RUN: diff %t1 %t2
409</pre>
410</div>
Reid Spencere2965482007-04-15 08:01:04 +0000[diff] [blame]411
Reid Spencer530eef62007-04-14 23:27:06 +0000[diff] [blame]412 <p>As with a Unix shell, the RUN: lines permit pipelines and I/O redirection
413 to be used. However, the usage is slightly different than for Bash. To check
414 what's legal, see the documentation for the
415 <a href="http://www.tcl.tk/man/tcl8.5/TclCmd/exec.htm#M2">Tcl exec</a>
416 command and the
417 <a href="http://www.tcl.tk/man/tcl8.5/tutorial/Tcl26.html">tutorial</a>.
418 The major differences are:</p>
419 <ul>
420 <li>You can't do <tt>2&gt;&amp;1</tt>. That will cause Tcl to write to a
421 file named <tt>&amp;1</tt>. Usually this is done to get stderr to go through
422 a pipe. You can do that in tcl with <tt>|&amp;</tt> so replace this idiom:
423 <tt>... 2&gt;&amp;1 | grep</tt> with <tt>... |&amp; grep</tt></li>
424 <li>You can only redirect to a file, not to another descriptor and not from
425 a here document.</li>
426 <li>tcl supports redirecting to open files with the @ syntax but you
427 shouldn't use that here.</li>
428 </ul>
429
Reid Spencere2965482007-04-15 08:01:04 +0000[diff] [blame]430 <p>There are some quoting rules that you must pay attention to when writing
431 your RUN lines. In general nothing needs to be quoted. Tcl won't strip off any
Daniel Dunbarf85eb932010-08-02 01:20:23 +0000[diff] [blame]432 quote characters so they will get passed to the invoked program. For
433 example:</p>
Bill Wendling6275c232007-09-22 09:16:44 +0000[diff] [blame]434
435<div class="doc_code">
436<pre>
437... | grep 'find this string'
438</pre>
439</div>
440
Reid Spencere2965482007-04-15 08:01:04 +0000[diff] [blame]441 <p>This will fail because the ' characters are passed to grep. This would
442 instruction grep to look for <tt>'find</tt> in the files <tt>this</tt> and
443 <tt>string'</tt>. To avoid this use curly braces to tell Tcl that it should
444 treat everything enclosed as one value. So our example would become:</p>
Bill Wendling6275c232007-09-22 09:16:44 +0000[diff] [blame]445
446<div class="doc_code">
447<pre>
448... | grep {find this string}
449</pre>
450</div>
451
Reid Spencere2965482007-04-15 08:01:04 +0000[diff] [blame]452 <p>Additionally, the characters <tt>[</tt> and <tt>]</tt> are treated
453 specially by Tcl. They tell Tcl to interpret the content as a command to
454 execute. Since these characters are often used in regular expressions this can
455 have disastrous results and cause the entire test run in a directory to fail.
456 For example, a common idiom is to look for some basicblock number:</p>
Bill Wendling6275c232007-09-22 09:16:44 +0000[diff] [blame]457
458<div class="doc_code">
459<pre>
460... | grep bb[2-8]
461</pre>
462</div>
463
Reid Spencere2965482007-04-15 08:01:04 +0000[diff] [blame]464 <p>This, however, will cause Tcl to fail because its going to try to execute
465 a program named "2-8". Instead, what you want is this:</p>
Bill Wendling6275c232007-09-22 09:16:44 +0000[diff] [blame]466
467<div class="doc_code">
468<pre>
469... | grep {bb\[2-8\]}
470</pre>
471</div>
472
Reid Spencere2965482007-04-15 08:01:04 +0000[diff] [blame]473 <p>Finally, if you need to pass the <tt>\</tt> character down to a program,
474 then it must be doubled. This is another Tcl special character. So, suppose
475 you had:
Bill Wendling6275c232007-09-22 09:16:44 +0000[diff] [blame]476
477<div class="doc_code">
478<pre>
479... | grep 'i32\*'
480</pre>
481</div>
482
Reid Spencere2965482007-04-15 08:01:04 +0000[diff] [blame]483 <p>This will fail to match what you want (a pointer to i32). First, the
484 <tt>'</tt> do not get stripped off. Second, the <tt>\</tt> gets stripped off
485 by Tcl so what grep sees is: <tt>'i32*'</tt>. That's not likely to match
486 anything. To resolve this you must use <tt>\\</tt> and the <tt>{}</tt>, like
487 this:</p>
Bill Wendling6275c232007-09-22 09:16:44 +0000[diff] [blame]488
489<div class="doc_code">
490<pre>
491... | grep {i32\\*}
492</pre>
493</div>
Reid Spencere2965482007-04-15 08:01:04 +0000[diff] [blame]494
Shantonu Sen89d5c412009-06-26 05:44:53 +0000[diff] [blame]495<p>If your system includes GNU <tt>grep</tt>, make sure
496that <tt>GREP_OPTIONS</tt> is not set in your environment. Otherwise,
497you may get invalid results (both false positives and false
498negatives).</p>
499
Reid Spencer9dcf4c22007-04-14 21:46:15 +0000[diff] [blame]500</div>
Tanya Lattner4d690182004-12-06 02:11:52 +0000[diff] [blame]501
Reid Spencer9dcf4c22007-04-14 21:46:15 +0000[diff] [blame]502<!-- _______________________________________________________________________ -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000[diff] [blame]503<h3><a name="FileCheck">The FileCheck utility</a></h3>
Chris Lattner7e11b722009-08-15 15:40:48 +0000[diff] [blame]504<!-- _______________________________________________________________________ -->
505
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000[diff] [blame]506<div>
Chris Lattner7e11b722009-08-15 15:40:48 +0000[diff] [blame]507
508<p>A powerful feature of the RUN: lines is that it allows any arbitrary commands
509 to be executed as part of the test harness. While standard (portable) unix
510 tools like 'grep' work fine on run lines, as you see above, there are a lot
Chris Lattner3ee64e82009-08-15 16:51:06 +0000[diff] [blame]511 of caveats due to interaction with Tcl syntax, and we want to make sure the
Chris Lattner7e11b722009-08-15 15:40:48 +0000[diff] [blame]512 run lines are portable to a wide range of systems. Another major problem is
513 that grep is not very good at checking to verify that the output of a tools
514 contains a series of different output in a specific order. The FileCheck
515 tool was designed to help with these problems.</p>
516
Chris Lattner3ee64e82009-08-15 16:51:06 +0000[diff] [blame]517<p>FileCheck (whose basic command line arguments are described in <a
518 href="http://llvm.org/cmds/FileCheck.html">the FileCheck man page</a> is
519 designed to read a file to check from standard input, and the set of things
520 to verify from a file specified as a command line argument. A simple example
521 of using FileCheck from a RUN line looks like this:</p>
522
523<div class="doc_code">
524<pre>
525; RUN: llvm-as &lt; %s | llc -march=x86-64 | <b>FileCheck %s</b>
526</pre>
527</div>
Chris Lattner7e11b722009-08-15 15:40:48 +0000[diff] [blame]528
Chris Lattner3ee64e82009-08-15 16:51:06 +0000[diff] [blame]529<p>This syntax says to pipe the current file ("%s") into llvm-as, pipe that into
530llc, then pipe the output of llc into FileCheck. This means that FileCheck will
531be verifying its standard input (the llc output) against the filename argument
532specified (the original .ll file specified by "%s"). To see how this works,
533lets look at the rest of the .ll file (after the RUN line):</p>
534
535<div class="doc_code">
536<pre>
537define void @sub1(i32* %p, i32 %v) {
538entry:
539; <b>CHECK: sub1:</b>
540; <b>CHECK: subl</b>
541 %0 = tail call i32 @llvm.atomic.load.sub.i32.p0i32(i32* %p, i32 %v)
542 ret void
543}
544
545define void @inc4(i64* %p) {
546entry:
547; <b>CHECK: inc4:</b>
548; <b>CHECK: incq</b>
549 %0 = tail call i64 @llvm.atomic.load.add.i64.p0i64(i64* %p, i64 1)
550 ret void
551}
552</pre>
553</div>
554
555<p>Here you can see some "CHECK:" lines specified in comments. Now you can see
556how the file is piped into llvm-as, then llc, and the machine code output is
557what we are verifying. FileCheck checks the machine code output to verify that
558it matches what the "CHECK:" lines specify.</p>
559
560<p>The syntax of the CHECK: lines is very simple: they are fixed strings that
561must occur in order. FileCheck defaults to ignoring horizontal whitespace
562differences (e.g. a space is allowed to match a tab) but otherwise, the contents
563of the CHECK: line is required to match some thing in the test file exactly.</p>
564
565<p>One nice thing about FileCheck (compared to grep) is that it allows merging
566test cases together into logical groups. For example, because the test above
567is checking for the "sub1:" and "inc4:" labels, it will not match unless there
568is a "subl" in between those labels. If it existed somewhere else in the file,
569that would not count: "grep subl" matches if subl exists anywhere in the
570file.</p>
571
Chris Lattnerda108b42009-08-15 18:32:21 +0000[diff] [blame]572<!-- _______________________________________________________________________ -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000[diff] [blame]573<h4>
574 <a name="FileCheck-check-prefix">The FileCheck -check-prefix option</a>
575</h4>
Chris Lattner3ee64e82009-08-15 16:51:06 +0000[diff] [blame]576
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000[diff] [blame]577<div>
Chris Lattnerda108b42009-08-15 18:32:21 +0000[diff] [blame]578
Chris Lattner3ee64e82009-08-15 16:51:06 +0000[diff] [blame]579<p>The FileCheck -check-prefix option allows multiple test configurations to be
580driven from one .ll file. This is useful in many circumstances, for example,
581testing different architectural variants with llc. Here's a simple example:</p>
582
Chris Lattner3ee64e82009-08-15 16:51:06 +0000[diff] [blame]583<div class="doc_code">
584<pre>
585; RUN: llvm-as &lt; %s | llc -mtriple=i686-apple-darwin9 -mattr=sse41 \
586; RUN: | <b>FileCheck %s -check-prefix=X32</b>
587; RUN: llvm-as &lt; %s | llc -mtriple=x86_64-apple-darwin9 -mattr=sse41 \
588; RUN: | <b>FileCheck %s -check-prefix=X64</b>
589
590define &lt;4 x i32&gt; @pinsrd_1(i32 %s, &lt;4 x i32&gt; %tmp) nounwind {
591 %tmp1 = insertelement &lt;4 x i32&gt; %tmp, i32 %s, i32 1
592 ret &lt;4 x i32&gt; %tmp1
593; <b>X32:</b> pinsrd_1:
594; <b>X32:</b> pinsrd $1, 4(%esp), %xmm0
595
596; <b>X64:</b> pinsrd_1:
597; <b>X64:</b> pinsrd $1, %edi, %xmm0
598}
599</pre>
600</div>
601
602<p>In this case, we're testing that we get the expected code generation with
603both 32-bit and 64-bit code generation.</p>
604
Chris Lattnerda108b42009-08-15 18:32:21 +0000[diff] [blame]605</div>
606
607<!-- _______________________________________________________________________ -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000[diff] [blame]608<h4>
609 <a name="FileCheck-CHECK-NEXT">The "CHECK-NEXT:" directive</a>
610</h4>
Chris Lattnerda108b42009-08-15 18:32:21 +0000[diff] [blame]611
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000[diff] [blame]612<div>
Chris Lattnerda108b42009-08-15 18:32:21 +0000[diff] [blame]613
614<p>Sometimes you want to match lines and would like to verify that matches
Duncan Sands75b5d272011-02-15 09:23:02 +0000[diff] [blame]615happen on exactly consecutive lines with no other lines in between them. In
Chris Lattnerda108b42009-08-15 18:32:21 +0000[diff] [blame]616this case, you can use CHECK: and CHECK-NEXT: directives to specify this. If
617you specified a custom check prefix, just use "&lt;PREFIX&gt;-NEXT:". For
618example, something like this works as you'd expect:</p>
619
620<div class="doc_code">
621<pre>
Chris Lattner724af2c2009-08-15 18:33:10 +0000[diff] [blame]622define void @t2(&lt;2 x double&gt;* %r, &lt;2 x double&gt;* %A, double %B) {
Chris Lattnerda108b42009-08-15 18:32:21 +0000[diff] [blame]623 %tmp3 = load &lt;2 x double&gt;* %A, align 16
624 %tmp7 = insertelement &lt;2 x double&gt; undef, double %B, i32 0
Chris Lattner724af2c2009-08-15 18:33:10 +0000[diff] [blame]625 %tmp9 = shufflevector &lt;2 x double&gt; %tmp3,
626 &lt;2 x double&gt; %tmp7,
627 &lt;2 x i32&gt; &lt; i32 0, i32 2 &gt;
Chris Lattnerda108b42009-08-15 18:32:21 +0000[diff] [blame]628 store &lt;2 x double&gt; %tmp9, &lt;2 x double&gt;* %r, align 16
629 ret void
630
631; <b>CHECK:</b> t2:
632; <b>CHECK:</b> movl 8(%esp), %eax
633; <b>CHECK-NEXT:</b> movapd (%eax), %xmm0
634; <b>CHECK-NEXT:</b> movhpd 12(%esp), %xmm0
635; <b>CHECK-NEXT:</b> movl 4(%esp), %eax
636; <b>CHECK-NEXT:</b> movapd %xmm0, (%eax)
637; <b>CHECK-NEXT:</b> ret
638}
639</pre>
640</div>
641
642<p>CHECK-NEXT: directives reject the input unless there is exactly one newline
643between it an the previous directive. A CHECK-NEXT cannot be the first
644directive in a file.</p>
Chris Lattner7e11b722009-08-15 15:40:48 +0000[diff] [blame]645
646</div>
647
648<!-- _______________________________________________________________________ -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000[diff] [blame]649<h4>
650 <a name="FileCheck-CHECK-NOT">The "CHECK-NOT:" directive</a>
651</h4>
Chris Lattner236d2d52009-09-20 22:35:26 +0000[diff] [blame]652
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000[diff] [blame]653<div>
Chris Lattner236d2d52009-09-20 22:35:26 +0000[diff] [blame]654
655<p>The CHECK-NOT: directive is used to verify that a string doesn't occur
Chris Lattner05593db2009-09-20 22:45:18 +0000[diff] [blame]656between two matches (or the first match and the beginning of the file). For
Chris Lattner236d2d52009-09-20 22:35:26 +0000[diff] [blame]657example, to verify that a load is removed by a transformation, a test like this
658can be used:</p>
659
660<div class="doc_code">
661<pre>
662define i8 @coerce_offset0(i32 %V, i32* %P) {
663 store i32 %V, i32* %P
664
665 %P2 = bitcast i32* %P to i8*
666 %P3 = getelementptr i8* %P2, i32 2
667
668 %A = load i8* %P3
669 ret i8 %A
670; <b>CHECK:</b> @coerce_offset0
671; <b>CHECK-NOT:</b> load
672; <b>CHECK:</b> ret i8
673}
674</pre>
675</div>
676
677</div>
678
679<!-- _______________________________________________________________________ -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000[diff] [blame]680<h4>
681 <a name="FileCheck-Matching">FileCheck Pattern Matching Syntax</a>
682</h4>
Chris Lattnerf08d2db2009-09-24 21:47:32 +0000[diff] [blame]683
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000[diff] [blame]684<div>
Chris Lattnerf08d2db2009-09-24 21:47:32 +0000[diff] [blame]685
686<p>The CHECK: and CHECK-NOT: directives both take a pattern to match. For most
687uses of FileCheck, fixed string matching is perfectly sufficient. For some
688things, a more flexible form of matching is desired. To support this, FileCheck
689allows you to specify regular expressions in matching strings, surrounded by
690double braces: <b>{{yourregex}}</b>. Because we want to use fixed string
691matching for a majority of what we do, FileCheck has been designed to support
692mixing and matching fixed string matching with regular expressions. This allows
693you to write things like this:</p>
694
695<div class="doc_code">
696<pre>
697; CHECK: movhpd <b>{{[0-9]+}}</b>(%esp), <b>{{%xmm[0-7]}}</b>
698</pre>
699</div>
700
701<p>In this case, any offset from the ESP register will be allowed, and any xmm
702register will be allowed.</p>
703
704<p>Because regular expressions are enclosed with double braces, they are
705visually distinct, and you don't need to use escape characters within the double
706braces like you would in C. In the rare case that you want to match double
707braces explicitly from the input, you can use something ugly like
708<b>{{[{][{]}}</b> as your pattern.</p>
709
710</div>
711
Chris Lattner8879e062009-09-27 07:56:52 +0000[diff] [blame]712<!-- _______________________________________________________________________ -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000[diff] [blame]713<h4>
714 <a name="FileCheck-Variables">FileCheck Variables</a>
715</h4>
Chris Lattnerf08d2db2009-09-24 21:47:32 +0000[diff] [blame]716
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000[diff] [blame]717<div>
Chris Lattner8879e062009-09-27 07:56:52 +0000[diff] [blame]718
719<p>It is often useful to match a pattern and then verify that it occurs again
720later in the file. For codegen tests, this can be useful to allow any register,
721but verify that that register is used consistently later. To do this, FileCheck
722allows named variables to be defined and substituted into patterns. Here is a
723simple example:</p>
724
725<div class="doc_code">
726<pre>
727; CHECK: test5:
Chris Lattner5e0c7472009-09-27 08:01:44 +0000[diff] [blame]728; CHECK: notw <b>[[REGISTER:%[a-z]+]]</b>
729; CHECK: andw {{.*}}<b>[[REGISTER]]</b>
Chris Lattner8879e062009-09-27 07:56:52 +0000[diff] [blame]730</pre>
731</div>
732
Chris Lattner5e0c7472009-09-27 08:01:44 +0000[diff] [blame]733<p>The first check line matches a regex (<tt>%[a-z]+</tt>) and captures it into
734the variables "REGISTER". The second line verifies that whatever is in REGISTER
735occurs later in the file after an "andw". FileCheck variable references are
736always contained in <tt>[[ ]]</tt> pairs, are named, and their names can be
737formed with the regex "<tt>[a-zA-Z][a-zA-Z0-9]*</tt>". If a colon follows the
738name, then it is a definition of the variable, if not, it is a use.</p>
Chris Lattner8879e062009-09-27 07:56:52 +0000[diff] [blame]739
740<p>FileCheck variables can be defined multiple times, and uses always get the
741latest value. Note that variables are all read at the start of a "CHECK" line
742and are all defined at the end. This means that if you have something like
743"<tt>CHECK: [[XYZ:.*]]x[[XYZ]]</tt>" that the check line will read the previous
744value of the XYZ variable and define a new one after the match is performed. If
745you need to do something like this you can probably take advantage of the fact
746that FileCheck is not actually line-oriented when it matches, this allows you to
747define two separate CHECK lines that match on the same line.
748</p>
749
Chris Lattner8879e062009-09-27 07:56:52 +0000[diff] [blame]750</div>
Chris Lattnerf08d2db2009-09-24 21:47:32 +0000[diff] [blame]751
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000[diff] [blame]752</div>
753
Chris Lattnerf08d2db2009-09-24 21:47:32 +0000[diff] [blame]754<!-- _______________________________________________________________________ -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000[diff] [blame]755<h3><a name="rtvars">Variables and substitutions</a></h3>
Matthijs Kooijmane7d45b12008-05-23 11:45:18 +0000[diff] [blame]756<!-- _______________________________________________________________________ -->
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000[diff] [blame]757<div>
Reid Spencer9dcf4c22007-04-14 21:46:15 +0000[diff] [blame]758 <p>With a RUN line there are a number of substitutions that are permitted. In
759 general, any Tcl variable that is available in the <tt>substitute</tt>
760 function (in <tt>test/lib/llvm.exp</tt>) can be substituted into a RUN line.
761 To make a substitution just write the variable's name preceded by a $.
762 Additionally, for compatibility reasons with previous versions of the test
763 library, certain names can be accessed with an alternate syntax: a % prefix.
764 These alternates are deprecated and may go away in a future version.
765 </p>
Bill Wendling6637c572007-09-22 09:20:07 +0000[diff] [blame]766 <p>Here are the available variable names. The alternate syntax is listed in
Reid Spencer9dcf4c22007-04-14 21:46:15 +0000[diff] [blame]767 parentheses.</p>
Bill Wendling6275c232007-09-22 09:16:44 +0000[diff] [blame]768
Reid Spencer9dcf4c22007-04-14 21:46:15 +0000[diff] [blame]769 <dl style="margin-left: 25px">
770 <dt><b>$test</b> (%s)</dt>
771 <dd>The full path to the test case's source. This is suitable for passing
772 on the command line as the input to an llvm tool.</dd>
Bill Wendling6275c232007-09-22 09:16:44 +0000[diff] [blame]773
Reid Spencer9dcf4c22007-04-14 21:46:15 +0000[diff] [blame]774 <dt><b>$srcdir</b></dt>
775 <dd>The source directory from where the "<tt>make check</tt>" was run.</dd>
Bill Wendling6275c232007-09-22 09:16:44 +0000[diff] [blame]776
Reid Spencer9dcf4c22007-04-14 21:46:15 +0000[diff] [blame]777 <dt><b>objdir</b></dt>
Bill Wendling6637c572007-09-22 09:20:07 +0000[diff] [blame]778 <dd>The object directory that corresponds to the <tt>$srcdir</tt>.</dd>
Bill Wendling6275c232007-09-22 09:16:44 +0000[diff] [blame]779
Reid Spencer9dcf4c22007-04-14 21:46:15 +0000[diff] [blame]780 <dt><b>subdir</b></dt>
781 <dd>A partial path from the <tt>test</tt> directory that contains the
782 sub-directory that contains the test source being executed.</dd>
Bill Wendling6275c232007-09-22 09:16:44 +0000[diff] [blame]783
Reid Spencer9dcf4c22007-04-14 21:46:15 +0000[diff] [blame]784 <dt><b>srcroot</b></dt>
785 <dd>The root directory of the LLVM src tree.</dd>
Bill Wendling6275c232007-09-22 09:16:44 +0000[diff] [blame]786
Reid Spencer9dcf4c22007-04-14 21:46:15 +0000[diff] [blame]787 <dt><b>objroot</b></dt>
788 <dd>The root directory of the LLVM object tree. This could be the same
789 as the srcroot.</dd>
Bill Wendling6275c232007-09-22 09:16:44 +0000[diff] [blame]790
Reid Spencer9dcf4c22007-04-14 21:46:15 +0000[diff] [blame]791 <dt><b>path</b><dt>
792 <dd>The path to the directory that contains the test case source. This is
793 for locating any supporting files that are not generated by the test, but
794 used by the test.</dd>
Bill Wendling6275c232007-09-22 09:16:44 +0000[diff] [blame]795
Reid Spencer9dcf4c22007-04-14 21:46:15 +0000[diff] [blame]796 <dt><b>tmp</b></dt>
797 <dd>The path to a temporary file name that could be used for this test case.
798 The file name won't conflict with other test cases. You can append to it if
799 you need multiple temporaries. This is useful as the destination of some
800 redirected output.</dd>
Bill Wendling6275c232007-09-22 09:16:44 +0000[diff] [blame]801
Reid Spencer9dcf4c22007-04-14 21:46:15 +0000[diff] [blame]802 <dt><b>target_triplet</b> (%target_triplet)</dt>
803 <dd>The target triplet that corresponds to the current host machine (the one
804 running the test cases). This should probably be called "host".<dd>
Bill Wendling6275c232007-09-22 09:16:44 +0000[diff] [blame]805
Reid Spencer9dcf4c22007-04-14 21:46:15 +0000[diff] [blame]806 <dt><b>link</b> (%link)</dt>
807 <dd>This full link command used to link LLVM executables. This has all the
808 configured -I, -L and -l options.</dd>
Bill Wendling6275c232007-09-22 09:16:44 +0000[diff] [blame]809
Reid Spencer9dcf4c22007-04-14 21:46:15 +0000[diff] [blame]810 <dt><b>shlibext</b> (%shlibext)</dt>
811 <dd>The suffix for the host platforms share library (dll) files. This
812 includes the period as the first character.</dd>
813 </dl>
814 <p>To add more variables, two things need to be changed. First, add a line in
815 the <tt>test/Makefile</tt> that creates the <tt>site.exp</tt> file. This will
816 "set" the variable as a global in the site.exp file. Second, in the
817 <tt>test/lib/llvm.exp</tt> file, in the substitute proc, add the variable name
818 to the list of "global" declarations at the beginning of the proc. That's it,
819 the variable can then be used in test scripts.</p>
820</div>
821
822<!-- _______________________________________________________________________ -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000[diff] [blame]823<h3><a name="rtfeatures">Other Features</a></h3>
Matthijs Kooijmane7d45b12008-05-23 11:45:18 +0000[diff] [blame]824<!-- _______________________________________________________________________ -->
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000[diff] [blame]825<div>
Reid Spencer9dcf4c22007-04-14 21:46:15 +0000[diff] [blame]826 <p>To make RUN line writing easier, there are several shell scripts located
Matthijs Kooijmane7d45b12008-05-23 11:45:18 +0000[diff] [blame]827 in the <tt>llvm/test/Scripts</tt> directory. This directory is in the PATH
828 when running tests, so you can just call these scripts using their name. For
829 example:</p>
Reid Spencer9dcf4c22007-04-14 21:46:15 +0000[diff] [blame]830 <dl>
831 <dt><b>ignore</b></dt>
832 <dd>This script runs its arguments and then always returns 0. This is useful
833 in cases where the test needs to cause a tool to generate an error (e.g. to
834 check the error output). However, any program in a pipeline that returns a
835 non-zero result will cause the test to fail. This script overcomes that
836 issue and nicely documents that the test case is purposefully ignoring the
837 result code of the tool</dd>
Bill Wendling6275c232007-09-22 09:16:44 +0000[diff] [blame]838
Reid Spencer9dcf4c22007-04-14 21:46:15 +0000[diff] [blame]839 <dt><b>not</b></dt>
840 <dd>This script runs its arguments and then inverts the result code from
841 it. Zero result codes become 1. Non-zero result codes become 0. This is
842 useful to invert the result of a grep. For example "not grep X" means
843 succeed only if you don't find X in the input.</dd>
844 </dl>
Tanya Lattner4d690182004-12-06 02:11:52 +0000[diff] [blame]845
Reid Spencer9dcf4c22007-04-14 21:46:15 +0000[diff] [blame]846 <p>Sometimes it is necessary to mark a test case as "expected fail" or XFAIL.
Daniel Dunbar6d914f82010-02-23 07:56:28 +0000[diff] [blame]847 You can easily mark a test as XFAIL just by including <tt>XFAIL: </tt> on a
Reid Spencer9dcf4c22007-04-14 21:46:15 +0000[diff] [blame]848 line near the top of the file. This signals that the test case should succeed
Daniel Dunbarf85eb932010-08-02 01:20:23 +0000[diff] [blame]849 if the test fails. Such test cases are counted separately by the testing tool. To
Reid Spencer9dcf4c22007-04-14 21:46:15 +0000[diff] [blame]850 specify an expected fail, use the XFAIL keyword in the comments of the test
851 program followed by a colon and one or more regular expressions (separated by
Daniel Dunbar6d914f82010-02-23 07:56:28 +0000[diff] [blame]852 a comma). The regular expressions allow you to XFAIL the test conditionally by
853 host platform. The regular expressions following the : are matched against the
854 target triplet for the host machine. If there is a match, the test is expected
855 to fail. If not, the test is expected to succeed. To XFAIL everywhere just
856 specify <tt>XFAIL: *</tt>. Here is an example of an <tt>XFAIL</tt> line:</p>
Bill Wendling6275c232007-09-22 09:16:44 +0000[diff] [blame]857
858<div class="doc_code">
859<pre>
Daniel Dunbar6d914f82010-02-23 07:56:28 +0000[diff] [blame]860; XFAIL: darwin,sun
Bill Wendling6275c232007-09-22 09:16:44 +0000[diff] [blame]861</pre>
862</div>
Tanya Lattner4d690182004-12-06 02:11:52 +0000[diff] [blame]863
Reid Spencer9dcf4c22007-04-14 21:46:15 +0000[diff] [blame]864 <p>To make the output more useful, the <tt>llvm_runtest</tt> function wil
865 scan the lines of the test case for ones that contain a pattern that matches
866 PR[0-9]+. This is the syntax for specifying a PR (Problem Report) number that
Matthijs Kooijmane7d45b12008-05-23 11:45:18 +0000[diff] [blame]867 is related to the test case. The number after "PR" specifies the LLVM bugzilla
Reid Spencer9dcf4c22007-04-14 21:46:15 +0000[diff] [blame]868 number. When a PR number is specified, it will be used in the pass/fail
869 reporting. This is useful to quickly get some context when a test fails.</p>
870
871 <p>Finally, any line that contains "END." will cause the special
872 interpretation of lines to terminate. This is generally done right after the
873 last RUN: line. This has two side effects: (a) it prevents special
874 interpretation of lines that are part of the test program, not the
875 instructions to the test case, and (b) it speeds things up for really big test
876 cases by avoiding interpretation of the remainder of the file.</p>
Tanya Lattner4d690182004-12-06 02:11:52 +0000[diff] [blame]877
878</div>
John Criswelle90fc1f2003-10-10 18:42:49 +0000[diff] [blame]879
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000[diff] [blame]880</div>
881
Reid Spencerae21b0b2004-09-05 20:07:26 +0000[diff] [blame]882<!--=========================================================================-->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000[diff] [blame]883<h2><a name="testsuitestructure">Test suite Structure</a></h2>
Reid Spencerae21b0b2004-09-05 20:07:26 +0000[diff] [blame]884<!--=========================================================================-->
John Criswelle90fc1f2003-10-10 18:42:49 +0000[diff] [blame]885
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000[diff] [blame]886<div>
Brian Gaeke739811d2003-10-23 18:10:28 +0000[diff] [blame]887
Matthijs Kooijmane7d45b12008-05-23 11:45:18 +0000[diff] [blame]888<p>The <tt>test-suite</tt> module contains a number of programs that can be compiled
889with LLVM and executed. These programs are compiled using the native compiler
890and various LLVM backends. The output from the program compiled with the
891native compiler is assumed correct; the results from the other programs are
892compared to the native program output and pass if they match.</p>
John Criswelle90fc1f2003-10-10 18:42:49 +0000[diff] [blame]893
Matthijs Kooijmane7d45b12008-05-23 11:45:18 +0000[diff] [blame]894<p>When executing tests, it is usually a good idea to start out with a subset of
895the available tests or programs. This makes test run times smaller at first and
896later on this is useful to investigate individual test failures. To run some
897test only on a subset of programs, simply change directory to the programs you
898want tested and run <tt>gmake</tt> there. Alternatively, you can run a different
899test using the <tt>TEST</tt> variable to change what tests or run on the
900selected programs (see below for more info).</p>
Misha Brukman773d6f62004-03-01 18:21:04 +0000[diff] [blame]901
Andrew Trick68aa18e42010-09-23 20:26:44 +0000[diff] [blame]902<p>In addition for testing correctness, the <tt>test-suite</tt> directory also
Matthijs Kooijmane7d45b12008-05-23 11:45:18 +0000[diff] [blame]903performs timing tests of various LLVM optimizations. It also records
904compilation times for the compilers and the JIT. This information can be
905used to compare the effectiveness of LLVM's optimizations and code
906generation.</p>
Misha Brukman773d6f62004-03-01 18:21:04 +0000[diff] [blame]907
Andrew Trick68aa18e42010-09-23 20:26:44 +0000[diff] [blame]908<p><tt>test-suite</tt> tests are divided into three types of tests: MultiSource,
Matthijs Kooijmane7d45b12008-05-23 11:45:18 +0000[diff] [blame]909SingleSource, and External.</p>
Reid Spencercce67552004-12-08 16:52:51 +0000[diff] [blame]910
Matthijs Kooijmane7d45b12008-05-23 11:45:18 +0000[diff] [blame]911<ul>
Andrew Trick68aa18e42010-09-23 20:26:44 +0000[diff] [blame]912<li><tt>test-suite/SingleSource</tt>
Matthijs Kooijmane7d45b12008-05-23 11:45:18 +0000[diff] [blame]913<p>The SingleSource directory contains test programs that are only a single
914source file in size. These are usually small benchmark programs or small
915programs that calculate a particular value. Several such programs are grouped
916together in each directory.</p></li>
Bill Wendling6275c232007-09-22 09:16:44 +0000[diff] [blame]917
Andrew Trick68aa18e42010-09-23 20:26:44 +0000[diff] [blame]918<li><tt>test-suite/MultiSource</tt>
Matthijs Kooijmane7d45b12008-05-23 11:45:18 +0000[diff] [blame]919<p>The MultiSource directory contains subdirectories which contain entire
920programs with multiple source files. Large benchmarks and whole applications
921go here.</p></li>
Bill Wendling6275c232007-09-22 09:16:44 +0000[diff] [blame]922
Andrew Trick68aa18e42010-09-23 20:26:44 +0000[diff] [blame]923<li><tt>test-suite/External</tt>
Matthijs Kooijmane7d45b12008-05-23 11:45:18 +0000[diff] [blame]924<p>The External directory contains Makefiles for building code that is external
925to (i.e., not distributed with) LLVM. The most prominent members of this
926directory are the SPEC 95 and SPEC 2000 benchmark suites. The <tt>External</tt>
Stuart Hastings6d437692009-05-21 20:23:59 +0000[diff] [blame]927directory does not contain these actual tests, but only the Makefiles that know
Matthijs Kooijmane7d45b12008-05-23 11:45:18 +0000[diff] [blame]928how to properly compile these programs from somewhere else. The presence and
Andrew Trick68aa18e42010-09-23 20:26:44 +0000[diff] [blame]929location of these external programs is configured by the test-suite
Matthijs Kooijmane7d45b12008-05-23 11:45:18 +0000[diff] [blame]930<tt>configure</tt> script.</p></li>
931</ul>
932
933<p>Each tree is then subdivided into several categories, including applications,
934benchmarks, regression tests, code that is strange grammatically, etc. These
935organizations should be relatively self explanatory.</p>
936
937<p>Some tests are known to fail. Some are bugs that we have not fixed yet;
Daniel Dunbarf85eb932010-08-02 01:20:23 +0000[diff] [blame]938others are features that we haven't added yet (or may never add). In the
939regression tests, the result for such tests will be XFAIL (eXpected FAILure).
940In this way, you can tell the difference between an expected and unexpected
941failure.</p>
Matthijs Kooijmane7d45b12008-05-23 11:45:18 +0000[diff] [blame]942
Matthijs Kooijman8fd28412008-06-24 12:58:31 +0000[diff] [blame]943<p>The tests in the test suite have no such feature at this time. If the
Matthijs Kooijmane7d45b12008-05-23 11:45:18 +0000[diff] [blame]944test passes, only warnings and other miscellaneous output will be generated. If
945a test fails, a large &lt;program&gt; FAILED message will be displayed. This
946will help you separate benign warnings from actual test failures.</p>
947
Misha Brukman773d6f62004-03-01 18:21:04 +0000[diff] [blame]948</div>
949
Reid Spencerae21b0b2004-09-05 20:07:26 +0000[diff] [blame]950<!--=========================================================================-->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000[diff] [blame]951<h2><a name="testsuiterun">Running the test suite</a></h2>
Reid Spencerae21b0b2004-09-05 20:07:26 +0000[diff] [blame]952<!--=========================================================================-->
Misha Brukman773d6f62004-03-01 18:21:04 +0000[diff] [blame]953
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000[diff] [blame]954<div>
Misha Brukman773d6f62004-03-01 18:21:04 +0000[diff] [blame]955
956<p>First, all tests are executed within the LLVM object directory tree. They
Reid Spencerae21b0b2004-09-05 20:07:26 +0000[diff] [blame]957<i>are not</i> executed inside of the LLVM source tree. This is because the
John Mosby169927e2009-03-30 18:56:53 +0000[diff] [blame]958test suite creates temporary files during execution.</p>
Misha Brukman773d6f62004-03-01 18:21:04 +0000[diff] [blame]959
Matthijs Kooijman8fd28412008-06-24 12:58:31 +0000[diff] [blame]960<p>To run the test suite, you need to use the following steps:</p>
Bill Wendling6275c232007-09-22 09:16:44 +0000[diff] [blame]961
Reid Spencerae21b0b2004-09-05 20:07:26 +0000[diff] [blame]962<ol>
John Mosbyb92a76f2009-03-30 04:37:51 +0000[diff] [blame]963 <li><tt>cd</tt> into the <tt>llvm/projects</tt> directory in your source tree.
964 </li>
Bill Wendling6275c232007-09-22 09:16:44 +0000[diff] [blame]965
966 <li><p>Check out the <tt>test-suite</tt> module with:</p>
967
968<div class="doc_code">
969<pre>
Matthijs Kooijman8fd28412008-06-24 12:58:31 +0000[diff] [blame]970% svn co http://llvm.org/svn/llvm-project/test-suite/trunk test-suite
Bill Wendling6275c232007-09-22 09:16:44 +0000[diff] [blame]971</pre>
972</div>
Stuart Hastings6d437692009-05-21 20:23:59 +0000[diff] [blame]973 <p>This will get the test suite into <tt>llvm/projects/test-suite</tt>.</p>
John Mosbyb92a76f2009-03-30 04:37:51 +0000[diff] [blame]974 </li>
Stuart Hastings6d437692009-05-21 20:23:59 +0000[diff] [blame]975 <li><p>Configure and build <tt>llvm</tt>.</p></li>
976 <li><p>Configure and build <tt>llvm-gcc</tt>.</p></li>
977 <li><p>Install <tt>llvm-gcc</tt> somewhere.</p></li>
978 <li><p><em>Re-configure</em> <tt>llvm</tt> from the top level of
979 each build tree (LLVM object directory tree) in which you want
980 to run the test suite, just as you do before building LLVM.</p>
981 <p>During the <em>re-configuration</em>, you must either: (1)
982 have <tt>llvm-gcc</tt> you just built in your path, or (2)
983 specify the directory where your just-built <tt>llvm-gcc</tt> is
984 installed using <tt>--with-llvmgccdir=$LLVM_GCC_DIR</tt>.</p>
985 <p>You must also tell the configure machinery that the test suite
986 is available so it can be configured for your build tree:</p>
Bill Wendling6275c232007-09-22 09:16:44 +0000[diff] [blame]987<div class="doc_code">
988<pre>
John Mosbyb92a76f2009-03-30 04:37:51 +0000[diff] [blame]989% cd $LLVM_OBJ_ROOT ; $LLVM_SRC_ROOT/configure [--with-llvmgccdir=$LLVM_GCC_DIR]
Bill Wendling6275c232007-09-22 09:16:44 +0000[diff] [blame]990</pre>
991</div>
John Mosbyb92a76f2009-03-30 04:37:51 +0000[diff] [blame]992 <p>[Remember that <tt>$LLVM_GCC_DIR</tt> is the directory where you
993 <em>installed</em> llvm-gcc, not its src or obj directory.]</p>
Matthijs Kooijman3f95ba02008-05-20 10:28:55 +0000[diff] [blame]994 </li>
995
John Mosbyb92a76f2009-03-30 04:37:51 +0000[diff] [blame]996 <li><p>You can now run the test suite from your build tree as follows:</p>
997<div class="doc_code">
998<pre>
999% cd $LLVM_OBJ_ROOT/projects/test-suite
1000% make
1001</pre>
1002</div>
1003 </li>
Reid Spencerae21b0b2004-09-05 20:07:26 +0000[diff] [blame]1004</ol>
1005<p>Note that the second and third steps only need to be done once. After you
1006have the suite checked out and configured, you don't need to do it again (unless
Matthijs Kooijman3f95ba02008-05-20 10:28:55 +0000[diff] [blame]1007the test code or configure script changes).</p>
Reid Spencerae21b0b2004-09-05 20:07:26 +0000[diff] [blame]1008
Matthijs Kooijmane7d45b12008-05-23 11:45:18 +0000[diff] [blame]1009<!-- _______________________________________________________________________ -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000[diff] [blame]1010<h3>
1011 <a name="testsuiteexternal">Configuring External Tests</a>
1012</h3>
Matthijs Kooijmane7d45b12008-05-23 11:45:18 +0000[diff] [blame]1013<!-- _______________________________________________________________________ -->
Misha Brukman773d6f62004-03-01 18:21:04 +0000[diff] [blame]1014
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000[diff] [blame]1015<div>
Stuart Hastings6d437692009-05-21 20:23:59 +0000[diff] [blame]1016<p>In order to run the External tests in the <tt>test-suite</tt>
1017 module, you must specify <i>--with-externals</i>. This
1018 must be done during the <em>re-configuration</em> step (see above),
1019 and the <tt>llvm</tt> re-configuration must recognize the
1020 previously-built <tt>llvm-gcc</tt>. If any of these is missing or
1021 neglected, the External tests won't work.</p>
Matthijs Kooijmane7d45b12008-05-23 11:45:18 +0000[diff] [blame]1022<dl>
Dale Johannesen40e3b202008-12-10 01:58:32 +0000[diff] [blame]1023<dt><i>--with-externals</i></dt>
1024<dt><i>--with-externals=&lt;<tt>directory</tt>&gt;</i></dt>
Matthijs Kooijmane7d45b12008-05-23 11:45:18 +0000[diff] [blame]1025</dl>
Dale Johannesen40e3b202008-12-10 01:58:32 +0000[diff] [blame]1026 This tells LLVM where to find any external tests. They are expected to be
1027 in specifically named subdirectories of &lt;<tt>directory</tt>&gt;.
1028 If <tt>directory</tt> is left unspecified,
1029 <tt>configure</tt> uses the default value
1030 <tt>/home/vadve/shared/benchmarks/speccpu2000/benchspec</tt>.
1031 Subdirectory names known to LLVM include:
1032 <dl>
1033 <dt>spec95</dt>
1034 <dt>speccpu2000</dt>
1035 <dt>speccpu2006</dt>
1036 <dt>povray31</dt>
1037 </dl>
1038 Others are added from time to time, and can be determined from
1039 <tt>configure</tt>.
Bill Wendling6275c232007-09-22 09:16:44 +0000[diff] [blame]1040</div>
1041
Matthijs Kooijmane7d45b12008-05-23 11:45:18 +0000[diff] [blame]1042<!-- _______________________________________________________________________ -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000[diff] [blame]1043<h3>
1044 <a name="testsuitetests">Running different tests</a>
1045</h3>
Matthijs Kooijmane7d45b12008-05-23 11:45:18 +0000[diff] [blame]1046<!-- _______________________________________________________________________ -->
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000[diff] [blame]1047<div>
Stuart Hastings6d437692009-05-21 20:23:59 +0000[diff] [blame]1048<p>In addition to the regular "whole program" tests, the <tt>test-suite</tt>
Matthijs Kooijmane7d45b12008-05-23 11:45:18 +0000[diff] [blame]1049module also provides a mechanism for compiling the programs in different ways.
Matthijs Kooijman8fd28412008-06-24 12:58:31 +0000[diff] [blame]1050If the variable TEST is defined on the <tt>gmake</tt> command line, the test system will
Matthijs Kooijmane7d45b12008-05-23 11:45:18 +0000[diff] [blame]1051include a Makefile named <tt>TEST.&lt;value of TEST variable&gt;.Makefile</tt>.
1052This Makefile can modify build rules to yield different results.</p>
Bill Wendling6275c232007-09-22 09:16:44 +0000[diff] [blame]1053
Matthijs Kooijmane7d45b12008-05-23 11:45:18 +0000[diff] [blame]1054<p>For example, the LLVM nightly tester uses <tt>TEST.nightly.Makefile</tt> to
1055create the nightly test reports. To run the nightly tests, run <tt>gmake
1056TEST=nightly</tt>.</p>
1057
1058<p>There are several TEST Makefiles available in the tree. Some of them are
1059designed for internal LLVM research and will not work outside of the LLVM
1060research group. They may still be valuable, however, as a guide to writing your
1061own TEST Makefile for any optimization or analysis passes that you develop with
1062LLVM.</p>
1063
Bill Wendling6275c232007-09-22 09:16:44 +0000[diff] [blame]1064</div>
Misha Brukman773d6f62004-03-01 18:21:04 +0000[diff] [blame]1065
Matthijs Kooijmane7d45b12008-05-23 11:45:18 +0000[diff] [blame]1066<!-- _______________________________________________________________________ -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000[diff] [blame]1067<h3>
1068 <a name="testsuiteoutput">Generating test output</a>
1069</h3>
Matthijs Kooijmane7d45b12008-05-23 11:45:18 +0000[diff] [blame]1070<!-- _______________________________________________________________________ -->
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000[diff] [blame]1071<div>
Matthijs Kooijmane7d45b12008-05-23 11:45:18 +0000[diff] [blame]1072 <p>There are a number of ways to run the tests and generate output. The most
1073 simple one is simply running <tt>gmake</tt> with no arguments. This will
1074 compile and run all programs in the tree using a number of different methods
1075 and compare results. Any failures are reported in the output, but are likely
1076 drowned in the other output. Passes are not reported explicitely.</p>
Misha Brukman773d6f62004-03-01 18:21:04 +0000[diff] [blame]1077
Matthijs Kooijmane7d45b12008-05-23 11:45:18 +0000[diff] [blame]1078 <p>Somewhat better is running <tt>gmake TEST=sometest test</tt>, which runs
1079 the specified test and usually adds per-program summaries to the output
1080 (depending on which sometest you use). For example, the <tt>nightly</tt> test
1081 explicitely outputs TEST-PASS or TEST-FAIL for every test after each program.
1082 Though these lines are still drowned in the output, it's easy to grep the
1083 output logs in the Output directories.</p>
Misha Brukman773d6f62004-03-01 18:21:04 +0000[diff] [blame]1084
Matthijs Kooijmane7d45b12008-05-23 11:45:18 +0000[diff] [blame]1085 <p>Even better are the <tt>report</tt> and <tt>report.format</tt> targets
1086 (where <tt>format</tt> is one of <tt>html</tt>, <tt>csv</tt>, <tt>text</tt> or
1087 <tt>graphs</tt>). The exact contents of the report are dependent on which
1088 <tt>TEST</tt> you are running, but the text results are always shown at the
1089 end of the run and the results are always stored in the
1090 <tt>report.&lt;type&gt;.format</tt> file (when running with
1091 <tt>TEST=&lt;type&gt;</tt>).
Chris Lattnerc4f22522004-06-24 20:53:09 +0000[diff] [blame]1092
Matthijs Kooijmane7d45b12008-05-23 11:45:18 +0000[diff] [blame]1093 The <tt>report</tt> also generate a file called
1094 <tt>report.&lt;type&gt;.raw.out</tt> containing the output of the entire test
1095 run.
Chris Lattnerc4f22522004-06-24 20:53:09 +0000[diff] [blame]1096</div>
1097
Chris Lattner17d145e2006-05-23 01:40:20 +0000[diff] [blame]1098<!-- _______________________________________________________________________ -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000[diff] [blame]1099<h3>
1100 <a name="testsuitecustom">Writing custom tests for the test suite</a>
1101</h3>
Chris Lattner17d145e2006-05-23 01:40:20 +0000[diff] [blame]1102<!-- _______________________________________________________________________ -->
1103
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000[diff] [blame]1104<div>
Chris Lattner17d145e2006-05-23 01:40:20 +0000[diff] [blame]1105
Matthijs Kooijman8fd28412008-06-24 12:58:31 +0000[diff] [blame]1106<p>Assuming you can run the test suite, (e.g. "<tt>gmake TEST=nightly report</tt>"
Chris Lattner17d145e2006-05-23 01:40:20 +0000[diff] [blame]1107should work), it is really easy to run optimizations or code generator
1108components against every program in the tree, collecting statistics or running
1109custom checks for correctness. At base, this is how the nightly tester works,
1110it's just one example of a general framework.</p>
1111
1112<p>Lets say that you have an LLVM optimization pass, and you want to see how
1113many times it triggers. First thing you should do is add an LLVM
1114<a href="ProgrammersManual.html#Statistic">statistic</a> to your pass, which
1115will tally counts of things you care about.</p>
1116
1117<p>Following this, you can set up a test and a report that collects these and
Andrew Trick68aa18e42010-09-23 20:26:44 +0000[diff] [blame]1118formats them for easy viewing. This consists of two files, a
Matthijs Kooijman8fd28412008-06-24 12:58:31 +0000[diff] [blame]1119"<tt>test-suite/TEST.XXX.Makefile</tt>" fragment (where XXX is the name of your
Andrew Trick68aa18e42010-09-23 20:26:44 +0000[diff] [blame]1120test) and a "<tt>test-suite/TEST.XXX.report</tt>" file that indicates how to
Chris Lattner17d145e2006-05-23 01:40:20 +0000[diff] [blame]1121format the output into a table. There are many example reports of various
Matthijs Kooijman8fd28412008-06-24 12:58:31 +0000[diff] [blame]1122levels of sophistication included with the test suite, and the framework is very
Chris Lattner17d145e2006-05-23 01:40:20 +0000[diff] [blame]1123general.</p>
1124
1125<p>If you are interested in testing an optimization pass, check out the
1126"libcalls" test as an example. It can be run like this:<p>
1127
1128<div class="doc_code">
1129<pre>
Matthijs Kooijman8fd28412008-06-24 12:58:31 +0000[diff] [blame]1130% cd llvm/projects/test-suite/MultiSource/Benchmarks # or some other level
Chris Lattner17d145e2006-05-23 01:40:20 +0000[diff] [blame]1131% make TEST=libcalls report
1132</pre>
1133</div>
1134
1135<p>This will do a bunch of stuff, then eventually print a table like this:</p>
1136
1137<div class="doc_code">
1138<pre>
1139Name | total | #exit |
1140...
1141FreeBench/analyzer/analyzer | 51 | 6 |
1142FreeBench/fourinarow/fourinarow | 1 | 1 |
1143FreeBench/neural/neural | 19 | 9 |
1144FreeBench/pifft/pifft | 5 | 3 |
1145MallocBench/cfrac/cfrac | 1 | * |
1146MallocBench/espresso/espresso | 52 | 12 |
1147MallocBench/gs/gs | 4 | * |
1148Prolangs-C/TimberWolfMC/timberwolfmc | 302 | * |
1149Prolangs-C/agrep/agrep | 33 | 12 |
1150Prolangs-C/allroots/allroots | * | * |
1151Prolangs-C/assembler/assembler | 47 | * |
1152Prolangs-C/bison/mybison | 74 | * |
1153...
1154</pre>
1155</div>
1156
1157<p>This basically is grepping the -stats output and displaying it in a table.
1158You can also use the "TEST=libcalls report.html" target to get the table in HTML
1159form, similarly for report.csv and report.tex.</p>
1160
Matthijs Kooijman8fd28412008-06-24 12:58:31 +0000[diff] [blame]1161<p>The source for this is in test-suite/TEST.libcalls.*. The format is pretty
Chris Lattner17d145e2006-05-23 01:40:20 +0000[diff] [blame]1162simple: the Makefile indicates how to run the test (in this case,
1163"<tt>opt -simplify-libcalls -stats</tt>"), and the report contains one line for
1164each column of the output. The first value is the header for the column and the
1165second is the regex to grep the output of the command for. There are lots of
1166example reports that can do fancy stuff.</p>
1167
1168</div>
1169
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000[diff] [blame]1170</div>
1171
Brian Gaeke739811d2003-10-23 18:10:28 +0000[diff] [blame]1172<!-- *********************************************************************** -->
John Criswelle90fc1f2003-10-10 18:42:49 +0000[diff] [blame]1173
Misha Brukman773d6f62004-03-01 18:21:04 +0000[diff] [blame]1174<hr>
1175<address>
1176 <a href="http://jigsaw.w3.org/css-validator/check/referer"><img
Misha Brukman86242e12008-12-11 17:34:48 +0000[diff] [blame]1177 src="http://jigsaw.w3.org/css-validator/images/vcss-blue" alt="Valid CSS"></a>
Misha Brukman773d6f62004-03-01 18:21:04 +0000[diff] [blame]1178 <a href="http://validator.w3.org/check/referer"><img
Misha Brukman86242e12008-12-11 17:34:48 +0000[diff] [blame]1179 src="http://www.w3.org/Icons/valid-html401-blue" alt="Valid HTML 4.01"></a>
Brian Gaeke739811d2003-10-23 18:10:28 +0000[diff] [blame]1180
Daniel Dunbarf85eb932010-08-02 01:20:23 +0000[diff] [blame]1181 John T. Criswell, Daniel Dunbar, Reid Spencer, and Tanya Lattner<br>
NAKAMURA Takumica46f5a2011-04-09 02:13:37 +0000[diff] [blame]1182 <a href="http://llvm.org/">The LLVM Compiler Infrastructure</a><br>
Misha Brukman773d6f62004-03-01 18:21:04 +0000[diff] [blame]1183 Last modified: $Date$
1184</address>
Brian Gaeke739811d2003-10-23 18:10:28 +0000[diff] [blame]1185</body>
John Criswelle90fc1f2003-10-10 18:42:49 +0000[diff] [blame]1186</html>