Lines Matching full:suite

1 test-suite Guide
27 2. Check out the `test-suite` module with:
30    % git clone https://github.com/llvm/llvm-test-suite.git test-suite
33 3. Create a build directory and use CMake to configure the suite. Use the
38    % mkdir test-suite-build
39    % cd test-suite-build
41            -C../test-suite/cmake/caches/O3.cmake \
42            ../test-suite
60    PASS: test-suite :: MultiSource/Applications/ALAC/decode/alacconvert-decode.test (1 of 474)
61 …********** TEST 'test-suite :: MultiSource/Applications/ALAC/decode/alacconvert-decode.test' RESUL…
67    PASS: test-suite :: MultiSource/Applications/ALAC/encode/alacconvert-encode.test (2 of 474)
77    % test-suite/utils/compare.py results.json
79    % test-suite/utils/compare.py results_a.json results_b.json
86 The test-suite contains benchmark and test programs.  The programs come with
87 reference outputs so that their correctness can be checked.  The suite comes
91 The test-suite is divided into several directories:
112    distributed with the test-suite. The most prominent members of this
135 The test-suite has configuration options to customize building and running the
139 % cd test-suite-build
182   build parts of the test-suite or to include external suites.  This option
199   comes with the test-suite.  The `perf` is usually available on linux systems.
213 - `-Ctest-suite/cmake/caches/<cachefile.cmake>`
215   Use a CMake cache.  The test-suite comes with several CMake caches which
230   % test-suite/utils/compare.py baseline.json
231   Warning: 'test-suite :: External/SPEC/CINT2006/403.gcc/403.gcc.test' has No metrics!
254   % test-suite/utils/compare.py -m compile_time baseline.json
255   % test-suite/utils/compare.py -m size.__text baseline.json
261   % test-suite/utils/compare.py --filter-short baseline.json experiment.json
275   % test-suite/utils/compare.py base0.json base1.json base2.json vs exp0.json exp1.json exp2.json
291 …acing (or linking) them into the `test-suite/test-suite-externals/xxx` directory (example: `test-s…
295 `test-suite/External/SPEC/README`.
305 You can build custom suites using the test-suite infrastructure. A custom suite
307 picked up automatically if placed into a subdirectory of the test-suite or when
311 % cmake -DTEST_SUITE_SUBDIRS=path/to/my/benchmark-suite ../test-suite
328         ../test-suite
356 `test-suite/cmake/caches/target-target-*-iphoneos-internal.cmake` CMake cache
374           -C ../test-suite/cmake/caches/target-arm64-iphoneos-internal.cmake \
376           ../test-suite
387 Running the test-suite via LNT
390 The LNT tool can run the test-suite. Use this when submitting test results to
392 …lvm.org/docs/lnt/tests.html#llvm-cmake-test-suite](https://llvm.org/docs/lnt/tests.html#llvm-cmake…
395 Running the test-suite via Makefiles (deprecated)
398 **Note**: The test-suite comes with a set of Makefiles that are considered
403 [test-suite Makefile Guide](TestSuiteMakefileGuide).