LLVM Test Results for $DateString

Sections:
Overview Changes Trends Programs Regression
Previous:
$PrevDaysList
Back to: Test Results LLVM Page |
Today's Test Results Overview
Lines Of Code over Time Click for larger view
## CVS Tree Overview: CVS Checkout Log $NumDirsInCVS dirs, $NumFilesInCVS files, $LOC lines of code, checked out in $CVSCheckoutTime seconds Compilation Log $BuildError Time to configure CVS tree: $ConfigTime seconds ($ConfigWallTime seconds wall time) 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: $WarningsList
Changes from Yesterday
## 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
Changes over Time
GNUplot charts showing a couple of things: Compile Time Testing Time Time to run some programs, say all of Olden Time to compile something, say Olden. Size of bytecode files for Olden
Program Tests
This section tests LLVM on a variety of programs in the test suite. This 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: Program - The name of the program for that row. GCCAS - Time to run LLVM optimizers on the program. Bytecode - The size of the bytecode for the program Instrs - The number of LLVM instructions in the compiled bytecode LLC compile - The time taken compile with LLC (the static backend) JIT codegen - The amount of time spent in the JIT itself, instead of executing the program. Machine code - The number of bytes of machine code generated by the JIT. GCC - The time taken to execute the program when compiled with GCC -O2. CBE - The time taken to execute the program after compilation through the C backend, compiled with -O2. LLC - How long does the program generated by the static backend LLC take to execute 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. GCC/LLC - The speed-up of the LLC output vs the native GCC output: greater than 1 is a speedup, less than 1 is a slowdown. GCC/CBE - The speed-up of the CBE output vs the native GCC output: greater than 1 is a speedup, less than 1 is a slowdown. A complete log of testing SingleSource, MultiSource, and External programs are available for further analysis. ## Programs/External
$ExternalProgramsTable
## Programs/MultiSource
$MultiSourceProgramsTable
## Programs/SingleSource
$SingleSourceProgramsTable
Regression Tests
Not yet implemented