diff --git a/utils/NightlyTestTemplate.html b/utils/NightlyTestTemplate.html index bf6894b88c6..299bd803f41 100644 --- a/utils/NightlyTestTemplate.html +++ b/utils/NightlyTestTemplate.html @@ -116,28 +116,33 @@ GNUplot charts showing a couple of things:

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:

+includes benchmark suites like the Olden, McCat, 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. A failure in the execution of any test is marked +with an asterisk: `*'. 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 - The time taken compile with LLC (the static backend) -
  6. NAT - The time taken to execute the program when compiled - with GCC -O3. -
  7. CBE - The time taken to execute the program after compilation - through the C Backend. If the diff fails, this a *. -
  8. LLC - The time taken to run LLC compiled program -
  9. JIT - How long does the program take to execute in the - Just-In-Time compiler. -
  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. +
  12. Program - The name of the program for that row.
    13. +
  13. GCCAS - Time to run LLVM optimizers on the program.
    14. +
  14. Bytecode - The size of the bytecode for the + program
    15. +
  15. Instrs - The number of LLVM instructions in the + compiled bytecode
    16. +
  16. LLC compile - The time taken compile with + LLC (the static backend)
    17. +
  17. JIT codegen - The amount of time spent in the + JIT itself, instead of executing the program.
    18. +
  18. Machine code - The number of bytes of machine + code generated by the JIT.
    19. +
  19. GCC - The time taken to execute the program when compiled + with GCC -O3.
    20. +
  20. CBE - The time taken to execute the program after + compilation through the C Backend.
    21. +
  21. LLC - How long does the program generated by the static + backend LLC take to execute
    22. +
  22. JIT - The amount of time spent running the + program with the JIT; this includes the code generation phase (listed above) + and actually running the program.

A complete log of testing is available