Previous: $PrevDaysList

Back to:
Test Results
LLVM Page

CVS Tree Overview:

• CVS Checkout Log
  Time to check out CVS tree: $CVSCheckoutTime seconds
  Number of directories in CVS: $NumDirsInCVS
  Number of files in CVS: $NumFilesInCVS
  Number of lines of code: $LOC
• Compilation Log
  $BuildError Time to build CVS tree: $BuildTime seconds ($BuildWallTime seconds wall time)
  Number of object files compiled: $NumObjects
  Number of libraries linked: $NumLibraries
  Number of executables linked: $NumExecutables
  

Warnings during the build:

Changes to CVS:

• Users who committed to CVS: $UserCommitList
• Users who updated from CVS: $UserUpdateList
• Added Files: $AddedFilesList
• Modified Files: $ModifiedFilesList
• Removed Files: $RemovedFilesList

Changes to Warnings:

• Warnings Added: $WarningsAdded
• Warnings Removed: $WarningsRemoved

Changes in the test suite:

• New Tests: $TestsAdded
• Removed Tests: $TestsRemoved
• Newly passing tests: $TestsFixed
• Newly failing tests: $TestsBroken

GNUplot charts showing a couple of things:

1. LOC in CVS
2. Compile Time
3. Testing Time
4. Time to run some programs, say all of Olden
5. Time to compile something, say Olden.
6. Size of bytecode files for Olden

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

Programs/SingleSource

Not yet implemented