Home
last modified time | relevance | path

Searched refs:tests (Results 1 – 25 of 2121) sorted by relevance

12345678910>>...85

/llvm-project-15.0.7/clang-tools-extra/unittests/clang-tidy/
H A DIncludeInserterTest.cpp205 #include "clang_tidy/tests/insert_includes_test_header.h" in TEST()
216 #include "clang_tidy/tests/insert_includes_test_header.h" in TEST()
235 #include "clang_tidy/tests/insert_includes_test_header.h" in TEST()
246 #include "clang_tidy/tests/insert_includes_test_header.h" in TEST()
266 #include "clang_tidy/tests/insert_includes_test_header.h" in TEST()
279 #include "clang_tidy/tests/insert_includes_test_header.h" in TEST()
301 #include "clang_tidy/tests/insert_includes_test_header.h" in TEST()
312 #include "clang_tidy/tests/insert_includes_test_header.h" in TEST()
331 #include "clang_tidy/tests/insert_includes_test_header.h" in TEST()
343 #include "clang_tidy/tests/insert_includes_test_header.h" in TEST()
[all …]
/llvm-project-15.0.7/llvm/utils/lit/
H A DCMakeLists.txt2 # until the tests are run as we need to copy it into
3 # a copy of the tests folder
5 "${CMAKE_CURRENT_SOURCE_DIR}/tests/lit.site.cfg.in"
11 # To work around this the tests and the configuration file are copied into the
12 # build directory just before running them. The tests are not copied over at
14 # tests being run.
16 COMMAND ${CMAKE_COMMAND} -E remove_directory "${CMAKE_CURRENT_BINARY_DIR}/tests"
17 …_COMMAND} -E copy_directory "${CMAKE_CURRENT_SOURCE_DIR}/tests" "${CMAKE_CURRENT_BINARY_DIR}/tests"
18 …AKE_COMMAND} -E copy "${CMAKE_CURRENT_BINARY_DIR}/lit.site.cfg" "${CMAKE_CURRENT_BINARY_DIR}/tests"
19 COMMENT "Preparing lit tests"
[all …]
H A DMANIFEST.in3 recursive-include tests *
7 prune tests/Output
8 prune tests/*/Output
9 prune tests/*/*/Output
10 prune tests/*/*/*/Output
/llvm-project-15.0.7/cross-project-tests/
H A DCMakeLists.txt1 # Cross project tests, for tests that require access to multiple projects across
3 # The subset inside debuginfo-tests invoke clang to generate programs with
10 debuginfo-tests/llvm-prettyprinters/gdb/llvm-support.cpp
33 debuginfo-tests/llvm-prettyprinters/gdb/mlir-support.cpp
44 # llgdb-tests/asan.c and other asan* files.
48 # llgdb-tests/safestack.c
53 # Many dexter tests depend on lldb.
69 add_lit_testsuite(check-cross-project "Running cross-project tests"
75 add_lit_testsuite(check-debuginfo "Running debuginfo tests"
76 ${CMAKE_CURRENT_BINARY_DIR}/debuginfo-tests
[all …]
/llvm-project-15.0.7/llvm/utils/lit/lit/
H A Dmain.py167 for t in tests:
171 def determine_order(tests, order): argument
176 random.shuffle(tests)
178 tests.sort(key=lambda t: t.getFullName())
218 workers = min(len(tests), opts.workers)
269 def print_histogram(tests): argument
276 def print_results(tests, elapsed, opts): argument
278 for test in tests:
287 def print_group(tests, code, shown_codes): argument
288 if not tests:
[all …]
H A Dreports.py21 def write_results(self, tests, elapsed): argument
23 tests = [t for t in tests if t.result.code not in unexecuted_codes]
34 for test in tests:
93 def write_results(self, tests, elapsed): argument
94 tests.sort(key=by_suite_and_test_path)
104 def _write_testsuite(self, file, suite, tests): argument
110 for test in tests:
198 def write_results(self, tests, elapsed): argument
200 tests = [t for t in tests if t.result.code not in unexecuted_codes]
206 for test in tests:
[all …]
/llvm-project-15.0.7/llvm/utils/lit/utils/
H A Dcheck-coverage32 rm -f tests/.coverage
33 find tests -name .coverage.\* -exec rm {} \;
39 find tests/* -name .coverage.\* -exec mv {} tests \;
42 (cd tests && python -m coverage combine)
45 (cd tests && python -m coverage report)
49 (cd tests && python -m coverage html)
/llvm-project-15.0.7/llvm/test/tools/llvm-dwarfdump/X86/
H A Dsimplified-template-names.s4 # Checking the LLVM side of cross-project-tests/debuginfo-tests/clang_llvm_roundtrip/simplified_tem…
24 ….loc 0 142 0 # cross-project-tests/debuginfo-tests/clang_llvm_roundtrip/si…
34 ….loc 0 142 44 prologue_end # cross-project-tests/debuginfo-tests/clang_llvm_roundtrip/si…
48 ….loc 0 182 0 # cross-project-tests/debuginfo-tests/clang_llvm_roundtrip/si…
58 ….loc 0 184 8 prologue_end # cross-project-tests/debuginfo-tests/clang_llvm_roundtrip/si…
61 ….loc 0 185 3 # cross-project-tests/debuginfo-tests/clang_llvm_roundtrip/si…
63 ….loc 0 186 3 # cross-project-tests/debuginfo-tests/clang_llvm_roundtrip/si…
65 ….loc 0 187 3 # cross-project-tests/debuginfo-tests/clang_llvm_roundtrip/si…
67 ….loc 0 188 3 # cross-project-tests/debuginfo-tests/clang_llvm_roundtrip/si…
69 ….loc 0 189 3 # cross-project-tests/debuginfo-tests/clang_llvm_roundtrip/si…
[all …]
/llvm-project-15.0.7/libc/docs/
H A Dfuzzing.rst4 Fuzz tests are used to ensure quality and security of LLVM-libc implementations.
5 All fuzz tests live under the directory named ``fuzzing``. Within this
8 ``libc-fuzzer`` builds all of the enabled fuzz tests (but does not run them).
10 Types of fuzz tests
13 As of this writing, there are two different kinds of fuzz tests. One kind are
14 the traditional fuzz tests which test one function at a time and only that
15 particular function. The other kind of tests are what we call as the
16 differential fuzz tests. These tests compare the behavior of LLVM libc
/llvm-project-15.0.7/libcxx/utils/
H A DCMakeLists.txt2 add_custom_target(libcxx-generate-public-header-transitive-inclusion-tests
4 COMMENT "Generate tests checking for mandated transitive includes in public headers.")
6 add_custom_target(libcxx-generate-public-header-tests
8 COMMENT "Generate tests for including public headers.")
12 COMMENT "Generate the <version> header and tests for feature test macros.")
15 DEPENDS libcxx-generate-public-header-transitive-inclusion-tests
16 libcxx-generate-public-header-tests
18 COMMENT "Create all the auto-generated files in libc++ and its tests.")
/llvm-project-15.0.7/libc/test/integration/loader/linux/
H A DCMakeLists.txt2 message("Skipping loader integration tests for target architecture ${LIBC_TARGET_ARCHITECTURE}.")
6 add_custom_target(libc-loader-tests)
7 add_dependencies(libc-integration-tests libc-loader-tests)
11 SUITE libc-loader-tests
25 SUITE libc-loader-tests
34 SUITE libc-loader-tests
43 SUITE libc-loader-tests
/llvm-project-15.0.7/compiler-rt/test/builtins/Unit/
H A Dudivmoddi4_test.c24 du_int tests[][4] = variable
20622 const unsigned N = sizeof(tests) / sizeof(tests[0]); in main()
20625 if (test__udivmoddi4(tests[i][0], tests[i][1], tests[i][2], tests[i][3])) in main()
H A Dumodsi3_test.c20 su_int tests[][4] = variable
158 const unsigned N = sizeof(tests) / sizeof(tests[0]); in main()
161 if (test__umodsi3(tests[i][0], tests[i][1], tests[i][2])) in main()
H A Dudivsi3_test.c20 su_int tests[][4] = variable
158 const unsigned N = sizeof(tests) / sizeof(tests[0]); in main()
161 if (test__udivsi3(tests[i][0], tests[i][1], tests[i][2])) in main()
H A Ddivmodti4_test.c55 tu_int tests[][4] = variable
80 const unsigned N = sizeof(tests) / sizeof(tests[0]); in main()
83 if (test__divmodti4(tests[i][0], tests[i][1], tests[i][2], tests[i][3])) in main()
/llvm-project-15.0.7/compiler-rt/test/builtins/Unit/arm/
H A Daeabi_uldivmod_test.c37 du_int tests[][4] = variable
20637 const unsigned N = sizeof(tests) / sizeof(tests[0]); in main()
20640 if (test_aeabi_uldivmod(tests[i][0], tests[i][1], tests[i][2], tests[i][3])) in main()
/llvm-project-15.0.7/polly/lib/External/isl/imath/tests/gmp-compat-test/
H A DREADME4 compatibility layer of imath. The tests cases are randomly generated
8 You should not see any failures when running these tests.
13 run these tests you will need the following items
22 All the tests cases will be generated and run automatically by the
26 Use the following command to generate and run the tests
28 $ make TESTS=random.tests
31 randomized unit tests. By default the unit tests are output to the
32 random.tests file. The tests can be run by hand using the following
35 $ ./runtest random.tests
98 gendata.py ~~generates~~> random.tests
[all …]
/llvm-project-15.0.7/lldb/third_party/Python/module/pexpect-4.6/
H A DDEVELOPERS.rst1 To run the tests, use `py.test <http://pytest.org/latest/>`_::
3 py.test tests
5 The tests are all located in the tests/ directory. To add a new unit
6 test all you have to do is create the file in the tests/ directory with a
12 in the tests directory, which sets up some convenient functionality.
/llvm-project-15.0.7/llvm/docs/CommandGuide/
H A Dlit.rst9 :program:`lit` [*options*] [*tests*]
139 failure in) certain tests.
151 certain tests.
153 .. option:: --time-tests
173 By default, `lit` will run failing tests first, then run tests in descending
192 .. option:: --max-tests=N
306 .. option:: --show-tests
337 tests in directories.
407 tests. :program:`lit` itself doesn't know how to run tests, rather this logic is
415 logic for finding those tests, and any additional information to run the tests.
[all …]
/llvm-project-15.0.7/mlir/test/
H A DCMakeLists.txt14 # for linalg integration tests.
19 # for the mlir spirv / vulkan runner tests.
25 "If set, arch-specific integration tests are run with Intel SDE.")
27 "If set, arch-specific Arm integration tests are run with an emulator.")
34 option(MLIR_RUN_AMX_TESTS "Run AMX tests.")
35 option(MLIR_RUN_X86VECTOR_TESTS "Run X86Vector tests.")
36 option(MLIR_RUN_CUDA_TENSOR_CORE_TESTS "Run CUDA Tensor core WMMA tests.")
37 option(MLIR_RUN_ARM_SVE_TESTS "Run Arm SVE tests.")
105 # run tests that involves executing on the host: do not build
165 # for the check-mlir target without executing the tests.
[all …]
/llvm-project-15.0.7/lldb/packages/Python/lldbsuite/test/test_runner/
H A DREADME.txt1 This directory contains source and tests for the lldb test runner
2 architecture. This directory is not for lldb python tests. It
3 is the test runner. The tests under this directory are test-runner
4 tests (i.e. tests that verify the test runner itself runs properly).
/llvm-project-15.0.7/third-party/benchmark/docs/
H A DAssemblyTests.md8 For these functions it's important to have tests that verify the
12 This document describes how the Benchmark library tests compiler output,
13 as well as how to properly write new tests.
42 specified in the tests source file. Please see the documentation
49 after the previous match, so tests should omit checks for unimportant
53 * The tests are compiled with `-O3 -g0`. So we're only testing the
77 Writing tests which check the code generated by a compiler are
79 versions may generate entirely different code. The Benchmark tests
109 Often tests require testing assembly lines which may subtly differ
134 build machine. Otherwise the tests will be disabled.
[all …]
/llvm-project-15.0.7/cross-project-tests/debuginfo-tests/dexter/
H A DREADME.md32 <compiler-executable> tests/nostdlib/fibonacci/test.cpp
46 The sample test case (tests/nostdlib/fibonacci) looks like this:
119 [1, "main", "c:\\dexter\\tests\\nostdlib\\fibonacci\\test.cpp", 23, 1, "BREAKPOINT", "FUNC", {}]
120 …[2, "main", "c:\\dexter\\tests\\nostdlib\\fibonacci\\test.cpp", 24, 1, "BREAKPOINT", "VERTICAL_FOR…
121 …[3, "main", "c:\\dexter\\tests\\nostdlib\\fibonacci\\test.cpp", 25, 1, "BREAKPOINT", "VERTICAL_FOR…
122 …. [4, "Fibonacci", "c:\\dexter\\tests\\nostdlib\\fibonacci\\test.cpp", 13, 1, "BREAKPOINT", "FUN…
143 …[25, "main", "c:\\dexter\\tests\\nostdlib\\fibonacci\\test.cpp", 26, 1, "BREAKPOINT", "FUNC", {"to…
272 …pass 7/211 = (0.7611) (0.0000) [Infer set function attributes on module (c:\dexter\tests\fibonac…
274 …pass 9/211 = (0.7611) (0.0000) [Called Value Propagation on module (c:\dexter\tests\fibonacci\te…
275 …pass 10/211 = (0.7611) (0.0000) [Global Variable Optimizer on module (c:\dexter\tests\fibonacci\…
[all …]
/llvm-project-15.0.7/compiler-rt/test/msan/Unit/
H A Dlit.site.cfg.py.in3 # Load common config for all compiler-rt unit tests.
9 # Setup test source and exec root. For unit tests, we define
10 # it as build directory with MSan unit tests.
11 # FIXME: Don't use hardcoded path to MSan unit tests.
12 config.test_exec_root = "@COMPILER_RT_BINARY_DIR@/lib/msan/tests"
/llvm-project-15.0.7/compiler-rt/test/builtins/Unit/ppc/
H A Dfloattitf_test.c35 expectedLongDouble.d[0] = tests[i].hi; in main()
36 expectedLongDouble.d[1] = tests[i].lo; in main()
37 result128 = tests[i].input128; in main()
47 (long long)(tests[i].input128 >> 64), in main()
48 (long long)tests[i].input128); in main()

12345678910>>...85