1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
2 "http://www.w3.org/TR/html4/strict.dtd">
5 <title>LLVM Test Suite Guide</title>
6 <link rel="stylesheet" href="llvm.css" type="text/css">
10 <div class="doc_title">
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>
20 <li><a href="#codefragments">Code Fragments</a></li>
21 <li><a href="#wholeprograms">Whole Programs</a></li>
24 <li><a href="#tree">LLVM Test Suite Tree</a></li>
25 <li><a href="#dgstructure">DejaGNU Structure</a></li>
26 <li><a href="#progstructure"><tt>llvm-test</tt> Structure</a></li>
27 <li><a href="#run">Running the LLVM Tests</a>
29 <li><a href="#customtest">Writing custom tests for llvm-test</a></li>
32 <li><a href="#nightly">Running the nightly tester</a></li>
35 <div class="doc_author">
36 <p>Written by John T. Criswell, <a
37 href="http://llvm.x10sys.com/rspencer">Reid Spencer</a>, and Tanya Lattner</p>
40 <!--=========================================================================-->
41 <div class="doc_section"><a name="overview">Overview</a></div>
42 <!--=========================================================================-->
44 <div class="doc_text">
46 <p>This document is the reference manual for the LLVM test suite. It documents
47 the structure of the LLVM test suite, the tools needed to use it, and how to add
52 <!--=========================================================================-->
53 <div class="doc_section"><a name="Requirements">Requirements</a></div>
54 <!--=========================================================================-->
56 <div class="doc_text">
58 <p>In order to use the LLVM test suite, you will need all of the software
59 required to build LLVM, plus the following:</p>
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>
66 <dt><a href="http://www.tcl.tk/software/tcltk/">tcl</a></dt>
67 <dd>Tcl is required by DejaGNU. </dd>
69 <dt><a href="http://www.netlib.org/f2c">F2C</a></dt>
70 <dd>For now, LLVM does not have a Fortran front-end, but using F2C, we can run
71 Fortran benchmarks. F2C support must be enabled via <tt>configure</tt> if not
72 installed in a standard place. F2C requires three items: the <tt>f2c</tt>
73 executable, <tt>f2c.h</tt> to compile the generated code, and <tt>libf2c.a</tt>
74 to link generated code. By default, given an F2C directory <tt>$DIR</tt>, the
75 configure 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
79 different location, you must tell <tt>configure</tt>:
82 <li><tt>./configure --with-f2c=$DIR</tt><br>
83 This will specify a new <tt>$DIR</tt> for the above-described search
84 process. This will only work if the binary, header, and library are in their
85 respective subdirectories of <tt>$DIR</tt>.</li>
87 <li><tt>./configure --with-f2c-bin=/binary/path --with-f2c-inc=/include/path
88 --with-f2c-lib=/lib/path</tt><br>
89 This allows you to specify the F2C components separately. Note: if you choose
90 this 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
92 filenames themselves on the <tt>configure</tt> line.</li>
96 <p>Darwin (Mac OS X) developers can simplify the installation of Expect and tcl
97 by using fink. <tt>fink install expect</tt> will install both. Alternatively,
98 Darwinports users can use <tt>sudo port install expect</tt> to install Expect
103 <!--=========================================================================-->
104 <div class="doc_section"><a name="quick">Quick Start</a></div>
105 <!--=========================================================================-->
107 <div class="doc_text">
109 <p>The tests are located in two separate CVS modules. The basic feature and
110 regression tests are in the main "llvm" module under the directory
111 <tt>llvm/test</tt>. A more comprehensive test suite that includes whole
112 programs in C and C++ is in the <tt>llvm-test</tt> module. This module should
113 be 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
115 will 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>
127 <p>To run only a subdirectory of tests in llvm/test using DejaGNU (ie.
128 Regression/Transforms), just set the TESTSUITE variable to the path of the
129 subdirectory (relative to <tt>llvm/test</tt>):</p>
131 % gmake -C llvm/test TESTSUITE=Regression/Transforms
134 <p><b>Note: If you are running the tests with <tt>objdir != subdir</tt>, you
135 must have run the complete testsuite before you can specify a
136 subdirectory.</b></p>
138 <p>To run the comprehensive test suite (tests that compile and execute whole
139 programs), run the <tt>llvm-test</tt> tests:</p>
145 % ./configure --with-llvmsrc=$LLVM_SRC_ROOT --with-llvmobj=$LLVM_OBJ_ROOT
151 <!--=========================================================================-->
152 <div class="doc_section"><a name="org">LLVM Test Suite Organization</a></div>
153 <!--=========================================================================-->
155 <div class="doc_text">
157 <p>The LLVM test suite contains two major categories of tests: code
158 fragments and whole programs. Code fragments are in the <tt>llvm</tt> module
159 under the <tt>llvm/test</tt> directory. The whole programs
160 test suite is in the <tt>llvm-test</tt> module under the main directory.</p>
164 <!-- _______________________________________________________________________ -->
165 <div class="doc_subsection"><a name="codefragments">Code Fragments</a></div>
166 <!-- _______________________________________________________________________ -->
168 <div class="doc_text">
170 <p>Code fragments are small pieces of code that test a specific feature of LLVM
171 or trigger a specific bug in LLVM. They are usually written in LLVM assembly
172 language, but can be written in other languages if the test targets a particular
173 language front end.</p>
175 <p>Code fragments are not complete programs, and they are never executed to
176 determine correct behavior.</p>
178 <p>These code fragment tests are located in the <tt>llvm/test/Features</tt> and
179 <tt>llvm/test/Regression</tt> directories.</p>
183 <!-- _______________________________________________________________________ -->
184 <div class="doc_subsection"><a name="wholeprograms">Whole Programs</a></div>
185 <!-- _______________________________________________________________________ -->
187 <div class="doc_text">
189 <p>Whole Programs are pieces of code which can be compiled and linked into a
190 stand-alone program that can be executed. These programs are generally written
191 in high level languages such as C or C++, but sometimes they are written
192 straight in LLVM assembly.</p>
194 <p>These programs are compiled and then executed using several different
195 methods (native compiler, LLVM C backend, LLVM JIT, LLVM native code generation,
196 etc). The output of these programs is compared to ensure that LLVM is compiling
197 the program correctly.</p>
199 <p>In addition to compiling and executing programs, whole program tests serve as
200 a way of benchmarking LLVM performance, both in terms of the efficiency of the
201 programs generated as well as the speed with which LLVM compiles, optimizes, and
204 <p>All "whole program" tests are located in the <tt>llvm-test</tt> CVS
209 <!--=========================================================================-->
210 <div class="doc_section"><a name="tree">LLVM Test Suite Tree</a></div>
211 <!--=========================================================================-->
213 <div class="doc_text">
215 <p>Each type of test in the LLVM test suite has its own directory. The major
216 subtrees of the test suite directory tree are as follows:</p>
219 <li><tt>llvm/test/Features</tt>
220 <p>This directory contains sample codes that test various features of the
221 LLVM language. These pieces of sample code are run through various
222 assembler, disassembler, and optimizer passes.</p>
225 <li><tt>llvm/test/Regression</tt>
226 <p>This directory contains regression tests for LLVM. When a bug is found
227 in LLVM, a regression test containing just enough code to reproduce the
228 problem should be written and placed somewhere underneath this directory.
229 In most cases, this will be a small piece of LLVM assembly language code,
230 often distilled from an actual application or benchmark.</p>
233 <li><tt>llvm-test</tt>
234 <p>The <tt>llvm-test</tt> CVS module contains programs that can be compiled
235 with LLVM and executed. These programs are compiled using the native compiler
236 and various LLVM backends. The output from the program compiled with the
237 native compiler is assumed correct; the results from the other programs are
238 compared to the native program output and pass if they match.</p>
240 <p>In addition for testing correctness, the <tt>llvm-test</tt> directory also
241 performs timing tests of various LLVM optimizations. It also records
242 compilation times for the compilers and the JIT. This information can be
243 used to compare the effectiveness of LLVM's optimizations and code
246 <li><tt>llvm-test/SingleSource</tt>
247 <p>The SingleSource directory contains test programs that are only a single
248 source file in size. These are usually small benchmark programs or small
249 programs that calculate a particular value. Several such programs are grouped
250 together in each directory.</p></li>
252 <li><tt>llvm-test/MultiSource</tt>
253 <p>The MultiSource directory contains subdirectories which contain entire
254 programs with multiple source files. Large benchmarks and whole applications
257 <li><tt>llvm-test/External</tt>
258 <p>The External directory contains Makefiles for building code that is external
259 to (i.e., not distributed with) LLVM. The most prominent members of this
260 directory are the SPEC 95 and SPEC 2000 benchmark suites. The presence and
261 location of these external programs is configured by the llvm-test
262 <tt>configure</tt> script.</p></li>
267 <!--=========================================================================-->
268 <div class="doc_section"><a name="dgstructure">DejaGNU Structure</a></div>
269 <!--=========================================================================-->
271 <div class="doc_text">
272 <p>The LLVM test suite is partially driven by DejaGNU and partially
273 driven by GNU Make. Specifically, the Features and Regression tests
274 are all driven by DejaGNU. The <tt>llvm-test</tt>
275 module is currently driven by a set of Makefiles.</p>
277 <p>The DejaGNU structure is very simple, but does require some
278 information to be set. This information is gathered via <tt>configure</tt> and
279 is written to a file, <tt>site.exp</tt> in <tt>llvm/test</tt>. The
281 Makefile does this work for you.</p>
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
285 the <tt>llvm-runtests</tt> procedure on each test file. The
286 llvm-runtests procedure is defined in
287 <tt>llvm/test/lib/llvm-dg.exp</tt>. Any directory that contains only
288 directories does not need the <tt>dg.exp</tt> file.</p>
290 <p>In order for a test to be run, it must contain information within
291 the test file on how to run the test. These are called <tt>RUN</tt>
292 lines. Run lines are specified in the comments of the test program
293 using the keyword <tt>RUN</tt> followed by a colon, and lastly the
294 commands to execute. These commands will be executed in a bash script,
295 so any bash syntax is acceptable. You can specify as many RUN lines as
296 necessary. Each RUN line translates to one line in the resulting bash
297 script. Below is an example of legal RUN lines in a <tt>.ll</tt>
300 ; RUN: llvm-as < %s | llvm-dis > %t1
301 ; RUN: llvm-dis < %s.bc-13 > %t2
304 <p>There are a couple patterns within a <tt>RUN</tt> line that the
305 llvm-runtest procedure looks for and replaces with the appropriate
308 <dl style="margin-left: 25px">
310 <dd>The path to the source directory. This is for locating
311 any supporting files that are not generated by the test, but used by
314 <dd>The test file.</dd>
317 <dd>Temporary filename: testscript.test_filename.tmp, where
318 test_filename is the name of the test file. All temporary files are
319 placed in the Output directory within the directory the test is
323 <dd>Path to a script that performs grep -C. Use this since not all
324 platforms support grep -C.</dd>
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>
330 <p>There are also several scripts in the llvm/test/Scripts directory
331 that you might find useful when writing <tt>RUN</tt> lines.</p>
333 <p>Lastly, you can easily mark a test that is expected to fail on a
334 specific platform or with a specific version of llvmgcc by using the
335 <tt>XFAIL</tt> keyword. Xfail lines are
336 specified in the comments of the test program using <tt>XFAIL</tt>,
337 followed by a colon, and one or more regular expressions (separated by
338 a comma) that will match against the target triplet or llvmgcc version for the
339 machine. 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
341 <tt>XFAIL</tt> line:</p>
343 ; XFAIL: darwin,sun,llvmgcc4
348 <!--=========================================================================-->
349 <div class="doc_section"><a name="progstructure"><tt>llvm-test</tt>
351 <!--=========================================================================-->
353 <div class="doc_text">
355 <p>As mentioned previously, the <tt>llvm-test</tt> module provides three types
356 of tests: MultiSource, SingleSource, and External. Each tree is then subdivided
357 into several categories, including applications, benchmarks, regression tests,
358 code that is strange grammatically, etc. These organizations should be
359 relatively self explanatory.</p>
361 <p>In addition to the regular "whole program" tests, the <tt>llvm-test</tt>
362 module also provides a mechanism for compiling the programs in different ways.
363 If the variable TEST is defined on the gmake command line, the test system will
364 include a Makefile named <tt>TEST.<value of TEST variable>.Makefile</tt>.
365 This Makefile can modify build rules to yield different results.</p>
367 <p>For example, the LLVM nightly tester uses <tt>TEST.nightly.Makefile</tt> to
368 create the nightly test reports. To run the nightly tests, run <tt>gmake
369 TEST=nightly</tt>.</p>
371 <p>There are several TEST Makefiles available in the tree. Some of them are
372 designed for internal LLVM research and will not work outside of the LLVM
373 research group. They may still be valuable, however, as a guide to writing your
374 own TEST Makefile for any optimization or analysis passes that you develop with
377 <p>Note, when configuring the <tt>llvm-test</tt> module, you might want to
378 specify the following configuration options:</p>
380 <dt><i>--enable-spec2000</i>
381 <dt><i>--enable-spec2000=<<tt>directory</tt>></i>
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>.
390 <dt><i>--enable-spec95</i>
391 <dt><i>--enable-spec95=<<tt>directory</tt>></i>
393 Enable the use of SPEC95 when testing LLVM. It is similar to the
394 <i>--enable-spec2000</i> option.
396 <dt><i>--enable-povray</i>
397 <dt><i>--enable-povray=<<tt>directory</tt>></i>
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>
405 <!--=========================================================================-->
406 <div class="doc_section"><a name="run">Running the LLVM Tests</a></div>
407 <!--=========================================================================-->
409 <div class="doc_text">
411 <p>First, all tests are executed within the LLVM object directory tree. They
412 <i>are not</i> executed inside of the LLVM source tree. This is because the
413 test suite creates temporary files during execution.</p>
415 <p>The master Makefile in llvm/test is capable of running only the DejaGNU
416 driven tests. By default, it will run all of these tests.</p>
418 <p>To run only the DejaGNU driven tests, run <tt>gmake</tt> at the
419 command line in <tt>llvm/test</tt>. To run a specific directory of tests, use
420 the TESTSUITE variable.
423 <p>For example, to run the Regression tests, type
424 <tt>gmake TESTSUITE=Regression</tt> in <tt>llvm/tests</tt>.</p>
426 <p>Note that there are no Makefiles in <tt>llvm/test/Features</tt> and
427 <tt>llvm/test/Regression</tt>. You must use DejaGNU from the <tt>llvm/test</tt>
428 directory to run them.</p>
430 <p>To run the <tt>llvm-test</tt> suite, you need to use the following steps:
433 <li>cd into the llvm/projects directory</li>
434 <li>check out the <tt>llvm-test</tt> module with:<br/>
435 <tt>cvs -d :pserver:anon@llvm.org:/var/cvs/llvm co -PR llvm-test</tt><br>
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:
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
445 <tt>$LLVM_SRC_ROOT/projects/llvm-test/configure
446 --with-llvmsrc=$LLVM_SRC_ROOT --with-llvmobj=$LLVM_OBJ_ROOT</tt>
451 <p>Note that the second and third steps only need to be done once. After you
452 have the suite checked out and configured, you don't need to do it again (unless
453 the test code or configure script changes).</p>
455 <p>To make a specialized test (use one of the
456 <tt>llvm-test/TEST.<type>.Makefile</tt>s), just run:<br/>
457 <tt>gmake TEST=<type> test</tt><br/>For example, you could run the
458 nightly tester tests using the following commands:</p>
461 % cd llvm/projects/llvm-test
462 % gmake TEST=nightly test
465 <p>Regardless of which test you're running, the results are printed on standard
466 output and standard error. You can redirect these results to a file if you
469 <p>Some tests are known to fail. Some are bugs that we have not fixed yet;
470 others are features that we haven't added yet (or may never add). In DejaGNU,
471 the result for such tests will be XFAIL (eXpected FAILure). In this way, you
472 can tell the difference between an expected and unexpected failure.</p>
474 <p>The tests in <tt>llvm-test</tt> have no such feature at this time. If the
475 test passes, only warnings and other miscellaneous output will be generated. If
476 a test fails, a large <program> FAILED message will be displayed. This
477 will help you separate benign warnings from actual test failures.</p>
481 <!-- _______________________________________________________________________ -->
482 <div class="doc_subsection">
483 <a name="customtest">Writing custom tests for llvm-test</a></div>
484 <!-- _______________________________________________________________________ -->
486 <div class="doc_text">
488 <p>Assuming you can run llvm-test, (e.g. "<tt>gmake TEST=nightly report</tt>"
489 should work), it is really easy to run optimizations or code generator
490 components against every program in the tree, collecting statistics or running
491 custom checks for correctness. At base, this is how the nightly tester works,
492 it's just one example of a general framework.</p>
494 <p>Lets say that you have an LLVM optimization pass, and you want to see how
495 many times it triggers. First thing you should do is add an LLVM
496 <a href="ProgrammersManual.html#Statistic">statistic</a> to your pass, which
497 will tally counts of things you care about.</p>
499 <p>Following this, you can set up a test and a report that collects these and
500 formats 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
502 test) and an "<tt>llvm-test/TEST.XXX.report</tt>" file that indicates how to
503 format the output into a table. There are many example reports of various
504 levels of sophistication included with llvm-test, and the framework is very
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>
510 <div class="doc_code">
512 % cd llvm/projects/llvm-test/MultiSource/Benchmarks # or some other level
513 % make TEST=libcalls report
517 <p>This will do a bunch of stuff, then eventually print a table like this:</p>
519 <div class="doc_code">
521 Name | total | #exit |
523 FreeBench/analyzer/analyzer | 51 | 6 |
524 FreeBench/fourinarow/fourinarow | 1 | 1 |
525 FreeBench/neural/neural | 19 | 9 |
526 FreeBench/pifft/pifft | 5 | 3 |
527 MallocBench/cfrac/cfrac | 1 | * |
528 MallocBench/espresso/espresso | 52 | 12 |
529 MallocBench/gs/gs | 4 | * |
530 Prolangs-C/TimberWolfMC/timberwolfmc | 302 | * |
531 Prolangs-C/agrep/agrep | 33 | 12 |
532 Prolangs-C/allroots/allroots | * | * |
533 Prolangs-C/assembler/assembler | 47 | * |
534 Prolangs-C/bison/mybison | 74 | * |
539 <p>This basically is grepping the -stats output and displaying it in a table.
540 You can also use the "TEST=libcalls report.html" target to get the table in HTML
541 form, similarly for report.csv and report.tex.</p>
543 <p>The source for this is in llvm-test/TEST.libcalls.*. The format is pretty
544 simple: 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
546 each column of the output. The first value is the header for the column and the
547 second is the regex to grep the output of the command for. There are lots of
548 example reports that can do fancy stuff.</p>
553 <!--=========================================================================-->
554 <div class="doc_section"><a name="nightly">Running the nightly tester</a></div>
555 <!--=========================================================================-->
557 <div class="doc_text">
560 The <a href="http://llvm.org/nightlytest/">LLVM Nightly Testers</a>
561 automatically check out an LLVM tree, build it, run the "nightly"
562 program test (described above), run all of the feature and regression tests,
563 delete the checked out tree, and then submit the results to
564 <a href="http://llvm.org/nightlytest/">http://llvm.org/nightlytest/</a>.
565 After test results are submitted to
566 <a href="http://llvm.org/nightlytest/">http://llvm.org/nightlytest/</a>,
567 they are processed and displayed on the tests page. An email to
568 <a href="http://lists.cs.uiuc.edu/pipermail/llvm-testresults/">
569 llvm-testresults@cs.uiuc.edu</a> summarizing the results is also generated.
570 This testing scheme is designed to ensure that programs don't break as well
571 as keep track of LLVM's progress over time.</p>
573 <p>If you'd like to set up an instance of the nightly tester to run on your
574 machine, 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
576 please choose a unique nickname and invoke <tt>utils/NewNightlyTest.pl</tt>
577 with the "-nickname [yournickname]" command line option. We usually run it
578 from a crontab entry that looks like this:</p>
580 <div class="doc_code">
582 5 3 * * * $HOME/llvm/utils/NewNightlyTest.pl -parallel -nickname Nickname \
583 $CVSROOT $HOME/buildtest $HOME/cvs/testresults
587 <p>Or, you can create a shell script to encapsulate the running of the script.
588 The optimized x86 Linux nightly test is run from just such a script:</p>
590 <div class="doc_code">
593 BASE=/proj/work/llvm/nightlytest
594 export CVSROOT=:pserver:anon@llvm.org:/var/cvs/llvm
595 export BUILDDIR=$BASE/build
596 export WEBDIR=$BASE/testresults
597 export LLVMGCCDIR=/proj/work/llvm/cfrontend/install
598 export PATH=/proj/install/bin:$LLVMGCCDIR/bin:$PATH
599 export LD_LIBRARY_PATH=/proj/install/lib
601 cp /proj/work/llvm/llvm/utils/NewNightlyTest.pl .
602 nice ./NewNightlyTest.pl -nice -release -verbose -parallel -enable-linscan \
603 -nickname NightlyTester -noexternals 2>&1 > output.log
607 <p>It is also possible to specify the the location your nightly test results
608 are 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
611 nightly test results page, you would invoke the nightly test script with
612 "-submit-server llvm.org -submit-script /nightlytest/NightlyTestAccept.cgi".
613 If these options are not specified, the nightly test script sends the results
614 to the llvm.org nightly test results page.</p>
616 <p>Take a look at the <tt>NewNightlyTest.pl</tt> file to see what all of the
617 flags and strings do. If you start running the nightly tests, please let us
622 <!-- *********************************************************************** -->
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>
631 John T. Criswell, Reid Spencer, and Tanya Lattner<br>
632 <a href="http://llvm.org">The LLVM Compiler Infrastructure</a><br/>
633 Last modified: $Date$