| blob | e4db61656bb79a155849dd3a22060deb2088153f |
3 <html>
4 <head>
7 </head>
8 <body>
11 LLVM Testing Infrastructure Guide
12 </div>
14 <ol>
18 <ul>
21 </ul>
22 </li>
24 <ul>
27 </ul>
28 </li>
30 <ul>
35 </ul>
36 </li>
39 <ul>
44 </ul>
45 </li>
46 </ol>
50 </div>
52 <!--=========================================================================-->
54 <!--=========================================================================-->
58 <p>This document is the reference manual for the LLVM testing infrastructure. It
59 documents the structure of the LLVM testing infrastructure, the tools needed to
60 use it, and how to add and run tests.</p>
62 </div>
64 <!--=========================================================================-->
66 <!--=========================================================================-->
70 <p>In order to use the LLVM testing infrastructure, you will need all of the
71 software required to build LLVM, as well
74 </div>
76 <!--=========================================================================-->
78 <!--=========================================================================-->
82 <p>The LLVM testing infrastructure contains two major categories of tests:
83 regression tests and whole programs. The regression tests are contained inside
85 pass -- they should be run before every commit. The whole programs tests are
87 in subversion.
88 </p>
90 </div>
92 <!-- _______________________________________________________________________ -->
94 <!-- _______________________________________________________________________ -->
98 <p>The regression tests are small pieces of code that test a specific feature of
99 LLVM or trigger a specific bug in LLVM. They are usually written in LLVM
100 assembly language, but can be written in other languages if the test targets a
103 tests are driven by the 'lit' testing tool, which is part of LLVM.</p>
105 <p>These code fragments are not complete programs. The code generated
106 from them is never executed to determine correct behavior.</p>
109 directory.</p>
111 <p>Typically when a bug is found in LLVM, a regression test containing
112 just enough code to reproduce the problem should be written and placed
113 somewhere underneath this directory. In most cases, this will be a small
114 piece of LLVM assembly language code, often distilled from an actual
115 application or benchmark.</p>
117 </div>
119 <!-- _______________________________________________________________________ -->
121 <!-- _______________________________________________________________________ -->
125 <p>The test suite contains whole programs, which are pieces of
126 code which can be compiled and linked into a stand-alone program that can be
127 executed. These programs are generally written in high level languages such as
128 C or C++, but sometimes they are written straight in LLVM assembly.</p>
130 <p>These programs are compiled and then executed using several different
131 methods (native compiler, LLVM C backend, LLVM JIT, LLVM native code generation,
132 etc). The output of these programs is compared to ensure that LLVM is compiling
133 the program correctly.</p>
135 <p>In addition to compiling and executing programs, whole program tests serve as
136 a way of benchmarking LLVM performance, both in terms of the efficiency of the
137 programs generated as well as the speed with which LLVM compiles, optimizes, and
138 generates code.</p>
142 </div>
144 <!--=========================================================================-->
146 <!--=========================================================================-->
150 <p>The tests are located in two separate Subversion modules. The regressions
151 tests are in the main "llvm" module under the directory
153 The more comprehensive test suite that includes whole
156 then the default "test-suite", for then the test suite will be run every time
162 <!-- _______________________________________________________________________ -->
164 <!-- _______________________________________________________________________ -->
165 <p>To run all of the LLVM regression tests, use master Makefile in
169 <pre>
170 % gmake -C llvm/test
171 </pre>
172 </div>
177 <pre>
178 % gmake check
179 </pre>
180 </div>
183 you can run the LLVM and Clang tests simultaneously using:</p>
188 <pre>
189 % gmake check-all
190 </pre>
191 </div>
193 <p>To run the tests with Valgrind (Memcheck by default), just append
197 <pre>
198 % gmake check VG=1
199 </pre>
200 </div>
202 <p>To run individual tests or subsets of tests, you can use the 'llvm-lit'
203 script which is built as part of LLVM. For example, to run the
204 'Integer/BitCast.ll' test by itself you can run:</p>
207 <pre>
208 % llvm-lit ~/llvm/test/Integer/BitCast.ll
209 </pre>
210 </div>
215 <pre>
216 % llvm-lit ~/llvm/test/CodeGen/ARM
217 </pre>
218 </div>
220 <p>For more information on using the 'lit' tool, see 'llvm-lit --help' or the
221 'lit' man page.</p>
223 <!-- _______________________________________________________________________ -->
225 <!-- _______________________________________________________________________ -->
227 <p>To run the comprehensive test suite (tests that compile and execute whole
231 <pre>
232 % cd llvm/projects
233 % svn co http://llvm.org/svn/llvm-project/test-suite/trunk test-suite
234 % cd ..
235 % ./configure --with-llvmgccdir=$LLVM_GCC_DIR
236 </pre>
237 </div>
245 respectively. If this is not the case,
247 executable's location.</p>
250 directory:</p>
253 <pre>
254 % cd projects/test-suite
255 % gmake
256 </pre>
257 </div>
260 let it generate a report by running:</p>
263 <pre>
264 % cd projects/test-suite
265 % gmake TEST=nightly report report.html
266 </pre>
267 </div>
269 <p>Any of the above commands can also be run in a subdirectory of
271 that subdirectory.</p>
273 </div>
275 <!--=========================================================================-->
277 <!--=========================================================================-->
279 <p>The LLVM regression tests are driven by 'lit' and are located in
282 <p>This directory contains a large array of small tests
283 that exercise various features of LLVM and to ensure that regressions do not
284 occur. The directory is broken into several sub-directories, each focused on
285 a particular area of LLVM. A few of the important ones are:</p>
287 <ul>
296 transforms to ensure they make the right transformations.</li>
298 </ul>
300 </div>
302 <!-- _______________________________________________________________________ -->
304 <!-- _______________________________________________________________________ -->
306 <p>The regression test structure is very simple, but does require some
310 you.</p>
312 <p>In order for the regression tests to work, each directory of tests must
314 run the tests. This file is just a Tcl script and it can do anything you want,
315 but we've standardized it for the LLVM regression tests. If you're adding a
319 defined in that library with a list of file names to run. The names are
320 obtained by using Tcl's glob command. Any directory that contains only
325 that specify how the test is to be run. So, each test script must contain
326 RUN lines if it is to do anything. If there are no RUN lines, the
328 fail.</p>
330 <p>RUN lines are specified in the comments of the test program using the
332 to execute. Together, these lines form the "script" that
334 RUN lines is similar to a shell's syntax for pipelines including I/O
335 redirection and variable substitution. However, even though these lines
338 shell. Consequently the syntax differs from normal shell script syntax in a
339 few ways. You can specify as many RUN lines as needed.</p>
341 <p>Each RUN line is executed on its own, distinct from other lines unless
343 line to be concatenated with the next one. In this way you can build up long
344 pipelines of commands without making huge line lengths. The lines ending in
346 found. This concatenated set of RUN lines then constitutes one execution.
347 Tcl will substitute variables and arrange for the pipeline to be executed. If
348 any process in the pipeline fails, the entire line (and test case) fails too.
349 </p>
354 <pre>
357 ; RUN: diff %t1 %t2
358 </pre>
359 </div>
361 <p>As with a Unix shell, the RUN: lines permit pipelines and I/O redirection
362 to be used. However, the usage is slightly different than for Bash. To check
363 what's legal, see the documentation for the
365 command and the
367 The major differences are:</p>
368 <ul>
373 <li>You can only redirect to a file, not to another descriptor and not from
374 a here document.</li>
375 <li>tcl supports redirecting to open files with the @ syntax but you
376 shouldn't use that here.</li>
377 </ul>
379 <p>There are some quoting rules that you must pay attention to when writing
380 your RUN lines. In general nothing needs to be quoted. Tcl won't strip off any
381 quote characters so they will get passed to the invoked program. For
382 example:</p>
385 <pre>
386 ... | grep 'find this string'
387 </pre>
388 </div>
390 <p>This will fail because the ' characters are passed to grep. This would
393 treat everything enclosed as one value. So our example would become:</p>
396 <pre>
397 ... | grep {find this string}
398 </pre>
399 </div>
402 specially by Tcl. They tell Tcl to interpret the content as a command to
403 execute. Since these characters are often used in regular expressions this can
404 have disastrous results and cause the entire test run in a directory to fail.
405 For example, a common idiom is to look for some basicblock number:</p>
408 <pre>
410 </pre>
411 </div>
413 <p>This, however, will cause Tcl to fail because its going to try to execute
417 <pre>
419 </pre>
420 </div>
423 then it must be doubled. This is another Tcl special character. So, suppose
424 you had:
427 <pre>
428 ... | grep 'i32\*'
429 </pre>
430 </div>
432 <p>This will fail to match what you want (a pointer to i32). First, the
436 this:</p>
439 <pre>
440 ... | grep {i32\\*}
441 </pre>
442 </div>
446 you may get invalid results (both false positives and false
447 negatives).</p>
449 </div>
451 <!-- _______________________________________________________________________ -->
453 <!-- _______________________________________________________________________ -->
457 <p>A powerful feature of the RUN: lines is that it allows any arbitrary commands
458 to be executed as part of the test harness. While standard (portable) unix
459 tools like 'grep' work fine on run lines, as you see above, there are a lot
460 of caveats due to interaction with Tcl syntax, and we want to make sure the
461 run lines are portable to a wide range of systems. Another major problem is
462 that grep is not very good at checking to verify that the output of a tools
463 contains a series of different output in a specific order. The FileCheck
464 tool was designed to help with these problems.</p>
468 designed to read a file to check from standard input, and the set of things
469 to verify from a file specified as a command line argument. A simple example
470 of using FileCheck from a RUN line looks like this:</p>
473 <pre>
475 </pre>
476 </div>
479 llc, then pipe the output of llc into FileCheck. This means that FileCheck will
480 be verifying its standard input (the llc output) against the filename argument
481 specified (the original .ll file specified by "%s"). To see how this works,
482 lets look at the rest of the .ll file (after the RUN line):</p>
485 <pre>
486 define void @sub1(i32* %p, i32 %v) {
487 entry:
490 %0 = tail call i32 @llvm.atomic.load.sub.i32.p0i32(i32* %p, i32 %v)
491 ret void
492 }
494 define void @inc4(i64* %p) {
495 entry:
499 ret void
500 }
501 </pre>
502 </div>
505 how the file is piped into llvm-as, then llc, and the machine code output is
506 what we are verifying. FileCheck checks the machine code output to verify that
509 <p>The syntax of the CHECK: lines is very simple: they are fixed strings that
510 must occur in order. FileCheck defaults to ignoring horizontal whitespace
511 differences (e.g. a space is allowed to match a tab) but otherwise, the contents
512 of the CHECK: line is required to match some thing in the test file exactly.</p>
514 <p>One nice thing about FileCheck (compared to grep) is that it allows merging
515 test cases together into logical groups. For example, because the test above
517 is a "subl" in between those labels. If it existed somewhere else in the file,
518 that would not count: "grep subl" matches if subl exists anywhere in the
519 file.</p>
521 </div>
523 <!-- _______________________________________________________________________ -->
529 <p>The FileCheck -check-prefix option allows multiple test configurations to be
530 driven from one .ll file. This is useful in many circumstances, for example,
531 testing different architectural variants with llc. Here's a simple example:</p>
534 <pre>
535 ; RUN: llvm-as < %s | llc -mtriple=i686-apple-darwin9 -mattr=sse41 \
537 ; RUN: llvm-as < %s | llc -mtriple=x86_64-apple-darwin9 -mattr=sse41 \
548 }
549 </pre>
550 </div>
552 <p>In this case, we're testing that we get the expected code generation with
555 </div>
557 <!-- _______________________________________________________________________ -->
563 <p>Sometimes you want to match lines and would like to verify that matches
564 happen on exactly consequtive lines with no other lines in between them. In
565 this case, you can use CHECK: and CHECK-NEXT: directives to specify this. If
566 you specified a custom check prefix, just use "<PREFIX>-NEXT:". For
567 example, something like this works as you'd expect:</p>
570 <pre>
578 ret void
587 }
588 </pre>
589 </div>
591 <p>CHECK-NEXT: directives reject the input unless there is exactly one newline
592 between it an the previous directive. A CHECK-NEXT cannot be the first
593 directive in a file.</p>
595 </div>
597 <!-- _______________________________________________________________________ -->
603 <p>The CHECK-NOT: directive is used to verify that a string doesn't occur
604 between two matches (or the first match and the beginning of the file). For
605 example, to verify that a load is removed by a transformation, a test like this
606 can be used:</p>
609 <pre>
610 define i8 @coerce_offset0(i32 %V, i32* %P) {
611 store i32 %V, i32* %P
613 %P2 = bitcast i32* %P to i8*
614 %P3 = getelementptr i8* %P2, i32 2
616 %A = load i8* %P3
617 ret i8 %A
621 }
622 </pre>
623 </div>
625 </div>
627 <!-- _______________________________________________________________________ -->
633 <p>The CHECK: and CHECK-NOT: directives both take a pattern to match. For most
634 uses of FileCheck, fixed string matching is perfectly sufficient. For some
635 things, a more flexible form of matching is desired. To support this, FileCheck
636 allows you to specify regular expressions in matching strings, surrounded by
638 matching for a majority of what we do, FileCheck has been designed to support
639 mixing and matching fixed string matching with regular expressions. This allows
640 you to write things like this:</p>
643 <pre>
645 </pre>
646 </div>
648 <p>In this case, any offset from the ESP register will be allowed, and any xmm
649 register will be allowed.</p>
651 <p>Because regular expressions are enclosed with double braces, they are
652 visually distinct, and you don't need to use escape characters within the double
653 braces like you would in C. In the rare case that you want to match double
654 braces explicitly from the input, you can use something ugly like
657 </div>
659 <!-- _______________________________________________________________________ -->
665 <p>It is often useful to match a pattern and then verify that it occurs again
666 later in the file. For codegen tests, this can be useful to allow any register,
667 but verify that that register is used consistently later. To do this, FileCheck
668 allows named variables to be defined and substituted into patterns. Here is a
669 simple example:</p>
672 <pre>
673 ; CHECK: test5:
676 </pre>
677 </div>
680 the variables "REGISTER". The second line verifies that whatever is in REGISTER
681 occurs later in the file after an "andw". FileCheck variable references are
683 formed with the regex "<tt>[a-zA-Z][a-zA-Z0-9]*</tt>". If a colon follows the
684 name, then it is a definition of the variable, if not, it is a use.</p>
686 <p>FileCheck variables can be defined multiple times, and uses always get the
687 latest value. Note that variables are all read at the start of a "CHECK" line
688 and are all defined at the end. This means that if you have something like
689 "<tt>CHECK: [[XYZ:.*]]x[[XYZ]]</tt>" that the check line will read the previous
690 value of the XYZ variable and define a new one after the match is performed. If
691 you need to do something like this you can probably take advantage of the fact
692 that FileCheck is not actually line-oriented when it matches, this allows you to
693 define two separate CHECK lines that match on the same line.
694 </p>
696 </div>
698 <!-- _______________________________________________________________________ -->
700 substitutions</a></div>
701 <!-- _______________________________________________________________________ -->
703 <p>With a RUN line there are a number of substitutions that are permitted. In
706 To make a substitution just write the variable's name preceded by a $.
707 Additionally, for compatibility reasons with previous versions of the test
708 library, certain names can be accessed with an alternate syntax: a % prefix.
709 These alternates are deprecated and may go away in a future version.
710 </p>
711 <p>Here are the available variable names. The alternate syntax is listed in
712 parentheses.</p>
716 <dd>The full path to the test case's source. This is suitable for passing
717 on the command line as the input to an llvm tool.</dd>
727 sub-directory that contains the test source being executed.</dd>
733 <dd>The root directory of the LLVM object tree. This could be the same
734 as the srcroot.</dd>
737 <dd>The path to the directory that contains the test case source. This is
738 for locating any supporting files that are not generated by the test, but
739 used by the test.</dd>
742 <dd>The path to a temporary file name that could be used for this test case.
743 The file name won't conflict with other test cases. You can append to it if
744 you need multiple temporaries. This is useful as the destination of some
745 redirected output.</dd>
751 <dd>The target triplet that corresponds to the current host machine (the one
756 configured LLVM environment</dd>
760 configured LLVM environment</dd>
764 this might not be gcc.</dd>
768 this might not be g++.</dd>
771 <dd>The full command line used to compile LLVM C source code. This has all
772 the configured -I, -D and optimization options.</dd>
775 <dd>The full command used to compile LLVM C++ source code. This has
776 all the configured -I, -D and optimization options.</dd>
779 <dd>This full link command used to link LLVM executables. This has all the
780 configured -I, -L and -l options.</dd>
783 <dd>The suffix for the host platforms share library (dll) files. This
784 includes the period as the first character.</dd>
785 </dl>
786 <p>To add more variables, two things need to be changed. First, add a line in
788 "set" the variable as a global in the site.exp file. Second, in the
790 to the list of "global" declarations at the beginning of the proc. That's it,
791 the variable can then be used in test scripts.</p>
792 </div>
794 <!-- _______________________________________________________________________ -->
796 <!-- _______________________________________________________________________ -->
798 <p>To make RUN line writing easier, there are several shell scripts located
800 when running tests, so you can just call these scripts using their name. For
801 example:</p>
802 <dl>
805 in cases where the test needs to cause a tool to generate an error (e.g. to
806 check the error output). However, any program in a pipeline that returns a
807 non-zero result will cause the test to fail. This script overcomes that
808 issue and nicely documents that the test case is purposefully ignoring the
809 result code of the tool</dd>
812 <dd>This script runs its arguments and then inverts the result code from
814 useful to invert the result of a grep. For example "not grep X" means
815 succeed only if you don't find X in the input.</dd>
816 </dl>
820 line near the top of the file. This signals that the test case should succeed
821 if the test fails. Such test cases are counted separately by the testing tool. To
822 specify an expected fail, use the XFAIL keyword in the comments of the test
823 program followed by a colon and one or more regular expressions (separated by
824 a comma). The regular expressions allow you to XFAIL the test conditionally by
825 host platform. The regular expressions following the : are matched against the
826 target triplet for the host machine. If there is a match, the test is expected
827 to fail. If not, the test is expected to succeed. To XFAIL everywhere just
831 <pre>
832 ; XFAIL: darwin,sun
833 </pre>
834 </div>
837 scan the lines of the test case for ones that contain a pattern that matches
839 is related to the test case. The number after "PR" specifies the LLVM bugzilla
840 number. When a PR number is specified, it will be used in the pass/fail
841 reporting. This is useful to quickly get some context when a test fails.</p>
844 interpretation of lines to terminate. This is generally done right after the
845 last RUN: line. This has two side effects: (a) it prevents special
846 interpretation of lines that are part of the test program, not the
847 instructions to the test case, and (b) it speeds things up for really big test
848 cases by avoiding interpretation of the remainder of the file.</p>
850 </div>
852 <!--=========================================================================-->
854 Structure</a></div>
855 <!--=========================================================================-->
860 with LLVM and executed. These programs are compiled using the native compiler
861 and various LLVM backends. The output from the program compiled with the
862 native compiler is assumed correct; the results from the other programs are
863 compared to the native program output and pass if they match.</p>
865 <p>When executing tests, it is usually a good idea to start out with a subset of
866 the available tests or programs. This makes test run times smaller at first and
867 later on this is useful to investigate individual test failures. To run some
868 test only on a subset of programs, simply change directory to the programs you
871 selected programs (see below for more info).</p>
874 performs timing tests of various LLVM optimizations. It also records
875 compilation times for the compilers and the JIT. This information can be
876 used to compare the effectiveness of LLVM's optimizations and code
877 generation.</p>
880 SingleSource, and External.</p>
882 <ul>
884 <p>The SingleSource directory contains test programs that are only a single
885 source file in size. These are usually small benchmark programs or small
886 programs that calculate a particular value. Several such programs are grouped
887 together in each directory.</p></li>
890 <p>The MultiSource directory contains subdirectories which contain entire
891 programs with multiple source files. Large benchmarks and whole applications
892 go here.</p></li>
895 <p>The External directory contains Makefiles for building code that is external
896 to (i.e., not distributed with) LLVM. The most prominent members of this
898 directory does not contain these actual tests, but only the Makefiles that know
899 how to properly compile these programs from somewhere else. The presence and
900 location of these external programs is configured by the llvm-test
902 </ul>
904 <p>Each tree is then subdivided into several categories, including applications,
905 benchmarks, regression tests, code that is strange grammatically, etc. These
906 organizations should be relatively self explanatory.</p>
908 <p>Some tests are known to fail. Some are bugs that we have not fixed yet;
909 others are features that we haven't added yet (or may never add). In the
910 regression tests, the result for such tests will be XFAIL (eXpected FAILure).
911 In this way, you can tell the difference between an expected and unexpected
912 failure.</p>
914 <p>The tests in the test suite have no such feature at this time. If the
915 test passes, only warnings and other miscellaneous output will be generated. If
917 will help you separate benign warnings from actual test failures.</p>
919 </div>
921 <!--=========================================================================-->
923 <!--=========================================================================-->
927 <p>First, all tests are executed within the LLVM object directory tree. They
929 test suite creates temporary files during execution.</p>
933 <ol>
935 </li>
940 <pre>
941 % svn co http://llvm.org/svn/llvm-project/test-suite/trunk test-suite
942 </pre>
943 </div>
945 </li>
950 each build tree (LLVM object directory tree) in which you want
951 to run the test suite, just as you do before building LLVM.</p>
956 <p>You must also tell the configure machinery that the test suite
957 is available so it can be configured for your build tree:</p>
959 <pre>
960 % cd $LLVM_OBJ_ROOT ; $LLVM_SRC_ROOT/configure [--with-llvmgccdir=$LLVM_GCC_DIR]
961 </pre>
962 </div>
965 </li>
969 <pre>
970 % cd $LLVM_OBJ_ROOT/projects/test-suite
971 % make
972 </pre>
973 </div>
974 </li>
975 </ol>
976 <p>Note that the second and third steps only need to be done once. After you
977 have the suite checked out and configured, you don't need to do it again (unless
978 the test code or configure script changes).</p>
980 </div>
982 <!-- _______________________________________________________________________ -->
985 <!-- _______________________________________________________________________ -->
993 neglected, the External tests won't work.</p>
994 <dl>
997 </dl>
998 This tells LLVM where to find any external tests. They are expected to be
1003 Subdirectory names known to LLVM include:
1004 <dl>
1009 </dl>
1010 Others are added from time to time, and can be determined from
1012 </div>
1014 <!-- _______________________________________________________________________ -->
1017 <!-- _______________________________________________________________________ -->
1020 module also provides a mechanism for compiling the programs in different ways.
1023 This Makefile can modify build rules to yield different results.</p>
1026 create the nightly test reports. To run the nightly tests, run <tt>gmake
1029 <p>There are several TEST Makefiles available in the tree. Some of them are
1030 designed for internal LLVM research and will not work outside of the LLVM
1031 research group. They may still be valuable, however, as a guide to writing your
1032 own TEST Makefile for any optimization or analysis passes that you develop with
1033 LLVM.</p>
1035 </div>
1037 <!-- _______________________________________________________________________ -->
1040 <!-- _______________________________________________________________________ -->
1042 <p>There are a number of ways to run the tests and generate output. The most
1044 compile and run all programs in the tree using a number of different methods
1045 and compare results. Any failures are reported in the output, but are likely
1046 drowned in the other output. Passes are not reported explicitely.</p>
1049 the specified test and usually adds per-program summaries to the output
1051 explicitely outputs TEST-PASS or TEST-FAIL for every test after each program.
1052 Though these lines are still drowned in the output, it's easy to grep the
1053 output logs in the Output directories.</p>
1059 end of the run and the results are always stored in the
1065 run.
1066 </div>
1068 <!-- _______________________________________________________________________ -->
1071 <!-- _______________________________________________________________________ -->
1076 should work), it is really easy to run optimizations or code generator
1077 components against every program in the tree, collecting statistics or running
1078 custom checks for correctness. At base, this is how the nightly tester works,
1079 it's just one example of a general framework.</p>
1081 <p>Lets say that you have an LLVM optimization pass, and you want to see how
1082 many times it triggers. First thing you should do is add an LLVM
1084 will tally counts of things you care about.</p>
1086 <p>Following this, you can set up a test and a report that collects these and
1087 formats them for easy viewing. This consists of two files, an
1088 "<tt>test-suite/TEST.XXX.Makefile</tt>" fragment (where XXX is the name of your
1089 test) and an "<tt>llvm-test/TEST.XXX.report</tt>" file that indicates how to
1090 format the output into a table. There are many example reports of various
1091 levels of sophistication included with the test suite, and the framework is very
1092 general.</p>
1094 <p>If you are interested in testing an optimization pass, check out the
1098 <pre>
1099 % cd llvm/projects/test-suite/MultiSource/Benchmarks # or some other level
1100 % make TEST=libcalls report
1101 </pre>
1102 </div>
1107 <pre>
1108 Name | total | #exit |
1109 ...
1114 MallocBench/cfrac/cfrac | 1 | * |
1116 MallocBench/gs/gs | 4 | * |
1117 Prolangs-C/TimberWolfMC/timberwolfmc | 302 | * |
1119 Prolangs-C/allroots/allroots | * | * |
1120 Prolangs-C/assembler/assembler | 47 | * |
1121 Prolangs-C/bison/mybison | 74 | * |
1122 ...
1123 </pre>
1124 </div>
1126 <p>This basically is grepping the -stats output and displaying it in a table.
1127 You can also use the "TEST=libcalls report.html" target to get the table in HTML
1128 form, similarly for report.csv and report.tex.</p>
1130 <p>The source for this is in test-suite/TEST.libcalls.*. The format is pretty
1131 simple: the Makefile indicates how to run the test (in this case,
1132 "<tt>opt -simplify-libcalls -stats</tt>"), and the report contains one line for
1133 each column of the output. The first value is the header for the column and the
1134 second is the regex to grep the output of the command for. There are lots of
1135 example reports that can do fancy stuff.</p>
1137 </div>
1139 <!-- *********************************************************************** -->
1141 <hr>
1142 <address>
1148 John T. Criswell, Daniel Dunbar, Reid Spencer, and Tanya Lattner<br>
1150 Last modified: $Date$
1151 </address>
1152 </body>
1153 </html>