Add support for program tests

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@5395 91177308-0d34-0410-b5e6-96231b3b80d8

1 files changed, 44 insertions, 2 deletions

diff --git a/utils/NightlyTestTemplate.html b/utils/NightlyTestTemplate.html
index ed00481..3b8ea2c 100644
--- a/utils/NightlyTestTemplate.html
+++ b/utils/NightlyTestTemplate.html
@@ -12,7 +12,7 @@
 <table border="0" cellspacing="0" cellpadding="2"><tr><td bgcolor="#000000"> 
 <table border="0" cellpadding="5" cellspacing="0"><tr><td bgcolor="#DDAA77">
 <font size=+1><b>Sections:</b></font><br>
-</td></tr><tr><td bgcolor="#FFCC99">
+</td></tr><tr><td bgcolor="#FFCC99" align=center>
 <a href="#Overview">Overview</a><br>
 <a href="#Changes">Changes</a><br>
 <a href="#Trends">Trends</a><br>
@@ -51,6 +51,7 @@
     Number of lines of code: <b>$LOC</b></ul>
 <li><a href="$DATE-Build-Log.txt">Compilation Log</a>
 <ul>
+    $BuildError
     Time to build CVS tree:      <b>$BuildTime</b> seconds<br>
     Number of object files compiled: <b>$NumObjects</b><br>
     Number of libraries linked: <b>$NumLibraries</b><br>
@@ -112,7 +113,48 @@ GNUplot <b>charts</b> showing a couple of things:
 <font size=+2 face=Verdana><b><a name="Programs">Program Tests</font></b>
 </td></tr></table></td></tr></table></center><p>
 
-Not yet implemented<p>
+This section tests LLVM on a variety of programs in the test suite.  This
+includes benchmark suites like the Olden, ptrdist, and SPEC benchmarks as well
+as a few random programs with test inputs.  This section is meant to track how
+stable LLVM is as a whole.  The columns of the tables are:<p>
+
+<ol>
+<li><a name="Program">Program - The name of the program for that row
+<li><a name="GCCAS">GCCAS - Time to run LLVM optimizers on the program
+<li><a name="Bytecode">Bytecode - The size of the bytecode for the program
+<li><a name="Instrs">Instrs - The number of LLVM instructions in the
+    compiled bytecode
+<li><a name="LLC">LLC - Does the program compile with the Sparc Backend?  Note
+    that this justs tests to see if the backend runs successfully, not if the
+    generated code works.
+<li><a name="CBE">CBE - Does the program compile with the C Backend?  Note
+    that this justs tests to see if the code generated compiles, not if it
+    works.
+<li><a name="LLI">LLI - How long does the program take to execute in
+    LLI's interpreter (note that this is capped to 30s).
+<li><a name="DynInstrs">DynInstrs - How many dynamic instructions are executed
+    by the interpreter, if it finishes.
+<li><a name="JIT">JIT - How long does the program take to execute in the
+    Just In Time compiler (again, capped to 30s).
+<li><a name="MachCode">MachCode - The number of bytes of machine code
+    generated by the JIT.
+<li><a name="CompTime">CompTime - The amount of time spent in the JIT itself,
+    instead of executing the program.
+</ol><p>
+
+A complete log of testing <a href="$DATE-ProgramTest.txt">is available</a> for
+further analysis.
+
+<h2>Programs/MultiSource</h2>
+
+<center>
+<table border="0" cellspacing="0" cellpadding="2"><tr><td bgcolor="#000000"> 
+$ProgramsTable
+</td></tr></table></center>
+
+<h2>Programs/SingleSource</h2>
+
+
 
 <br><br><center>
 <table border="0" cellspacing="0" cellpadding="2"><tr><td bgcolor="#000000">