From: Chris Lattner Date: Wed, 22 Jan 2003 16:13:10 +0000 (+0000) Subject: Add support for program tests X-Git-Url: http://plrg.eecs.uci.edu/git/?a=commitdiff_plain;h=8a4baf4f554fd18a5b7533747b9624eb13377adf;p=oota-llvm.git Add support for program tests git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@5395 91177308-0d34-0410-b5e6-96231b3b80d8 --- diff --git a/utils/NightlyTestTemplate.html b/utils/NightlyTestTemplate.html index ed00481a910..3b8ea2c3692 100644 --- a/utils/NightlyTestTemplate.html +++ b/utils/NightlyTestTemplate.html @@ -12,7 +12,7 @@
Sections:
-
+
Overview
Changes
Trends
@@ -51,6 +51,7 @@ Number of lines of code: $LOC
  • Compilation Log
      + $BuildError Time to build CVS tree: $BuildTime seconds
      Number of object files compiled: $NumObjects
      Number of libraries linked: $NumLibraries
      @@ -112,7 +113,48 @@ GNUplot charts showing a couple of things: Program Tests
  • -Not yet implemented

    +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:

    + +

      +
    1. Program - The name of the program for that row +
    2. GCCAS - Time to run LLVM optimizers on the program +
    3. Bytecode - The size of the bytecode for the program +
    4. Instrs - The number of LLVM instructions in the + compiled bytecode +
    5. 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. +
    6. 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. +
    7. LLI - How long does the program take to execute in + LLI's interpreter (note that this is capped to 30s). +
    8. DynInstrs - How many dynamic instructions are executed + by the interpreter, if it finishes. +
    9. JIT - How long does the program take to execute in the + Just In Time compiler (again, capped to 30s). +
    10. MachCode - The number of bytes of machine code + generated by the JIT. +
    11. CompTime - The amount of time spent in the JIT itself, + instead of executing the program. +

    + +A complete log of testing is available for +further analysis. + +

    Programs/MultiSource

    + +
    +
    +$ProgramsTable +
    + +

    Programs/SingleSource

    + +