Searched full:coverage (Results 1 – 25 of 4915) sorted by relevance
12345678910>>...197
| /external/clang/test/Driver/ |
| D | fsanitize-coverage.c | 1 …nux-gnu -fsanitize=address -fsanitize-coverage=0 %s -### 2>&1 | FileCheck %s --check-prefix=CHECK-…
2 …itize=address -fsanitize-coverage=edge -fsanitize-coverage=0 %s -### 2>&1 | FileCheck %s --check-p…
3 …4-linux-gnu -fsanitize=address %s -### 2>&1 | FileCheck %s --check-prefix=CHECK-SANITIZE-COVERAGE-0
4 // CHECK-SANITIZE-COVERAGE-0-NOT: fsanitize-coverage-type
5 // CHECK-SANITIZE-COVERAGE-0: -fsanitize=address
7 …x-gnu -fsanitize=address -fsanitize-coverage=func %s -### 2>&1 | FileCheck %s --check-prefix=CHECK…
8 …ux-gnu -fsanitize=memory -fsanitize-coverage=func %s -### 2>&1 | FileCheck %s --check-prefix=CHECK…
9 …inux-gnu -fsanitize=leak -fsanitize-coverage=func %s -### 2>&1 | FileCheck %s --check-prefix=CHECK…
10 …gnu -fsanitize=undefined -fsanitize-coverage=func %s -### 2>&1 | FileCheck %s --check-prefix=CHECK…
11 …inux-gnu -fsanitize=bool -fsanitize-coverage=func %s -### 2>&1 | FileCheck %s --check-prefix=CHECK…
[all …]
|
| /external/compiler-rt/test/asan/TestCases/Android/ |
| D | coverage-android.cc | 1 // Test for direct coverage writing with dlopen.
3 // Test normal exit, coverage level 1.
4 // RUN: %clangxx_asan -fsanitize-coverage=func -DSHARED %s -shared -o %T/libcoverage_android_test_1…
5 // RUN: %clangxx_asan -fsanitize-coverage=func -DSO_DIR=\"%device\" %s -o %t
7 // RUN: adb shell rm -rf %device/coverage-android
8 // RUN: rm -rf %T/coverage-android
10 // RUN: adb shell mkdir -p %device/coverage-android/direct
11 // RUN: mkdir -p %T/coverage-android/direct
12 // RUN: %env_asan_opts=coverage=1:coverage_direct=1:coverage_dir=%device/coverage-android/direct:ve…
13 // RUN: adb pull %device/coverage-android/direct %T/coverage-android/direct
[all …]
|
| /external/compiler-rt/test/asan/TestCases/Posix/ |
| D | coverage-direct.cc | 1 // Test for direct coverage writing with dlopen at coverage level 1 to 3.
3 // RUN: %clangxx_asan -fsanitize-coverage=func -DSHARED %s -shared -o %dynamiclib -fPIC
4 // RUN: %clangxx_asan -fsanitize-coverage=func %s %libdl -o %t
6 // RUN: rm -rf %T/coverage-direct
8 // RUN: mkdir -p %T/coverage-direct/normal
9 // RUN: %env_asan_opts=coverage=1:coverage_direct=0:coverage_dir=%T/coverage-direct/normal:verbosit…
10 // RUN: %sancov print %T/coverage-direct/normal/*.sancov >%T/coverage-direct/normal/out.txt
12 // RUN: mkdir -p %T/coverage-direct/direct
13 // RUN: %env_asan_opts=coverage=1:coverage_direct=1:coverage_dir=%T/coverage-direct/direct:verbosit…
14 // RUN: cd %T/coverage-direct/direct
[all …]
|
| D | coverage-direct-activation.cc | 1 // Test for direct coverage writing enabled at activation time.
3 // RUN: %clangxx_asan -fsanitize-coverage=func -DSHARED %s -shared -o %dynamiclib -fPIC
5 // RUN: %clangxx_asan -fsanitize-coverage=func %t.o %libdl -o %t
7 // RUN: rm -rf %T/coverage-direct-activation
9 // RUN: mkdir -p %T/coverage-direct-activation/normal
10 // RUN: %env_asan_opts=coverage=1,coverage_direct=0,coverage_dir=%T/coverage-direct-activation/norm…
11 // RUN: %sancov print %T/coverage-direct-activation/normal/*.sancov >%T/coverage-direct-activation/…
13 // RUN: mkdir -p %T/coverage-direct-activation/direct
15 // RUN: ASAN_ACTIVATION_OPTIONS=coverage=1,coverage_dir=%T/coverage-direct-activation/direct %run…
16 // RUN: cd %T/coverage-direct-activation/direct
[all …]
|
| /external/mbedtls/scripts/ |
| D | lcov.sh | 6 Collect coverage statistics of library code into an HTML report.
9 1. Build the library with CFLAGS="--coverage -O0 -g3" and link the test
10 programs with LDFLAGS="--coverage".
13 make CFLAGS="--coverage -O0 -g3" LDFLAGS="--coverage"
15 mkdir build-coverage && cd build-coverage &&
16 cmake -D CMAKE_BUILD_TYPE=Coverage .. && make
19 object files and coverage statistics files.
20 4. Browse the coverage report in Coverage/index.html.
35 rm -rf Coverage
36 mkdir Coverage Coverage/tmp
[all …]
|
| /external/openthread/third_party/mbedtls/repo/scripts/ |
| D | lcov.sh | 6 Collect coverage statistics of library code into an HTML report.
9 1. Build the library with CFLAGS="--coverage -O0 -g3" and link the test
10 programs with LDFLAGS="--coverage".
13 make CFLAGS="--coverage -O0 -g3" LDFLAGS="--coverage"
15 mkdir build-coverage && cd build-coverage &&
16 cmake -D CMAKE_BUILD_TYPE=Coverage .. && make
19 object files and coverage statistics files.
20 4. Browse the coverage report in Coverage/index.html.
35 rm -rf Coverage
36 mkdir Coverage Coverage/tmp
[all …]
|
| /external/rust/crates/grpcio-sys/grpc/third_party/cares/cares/m4/ |
| D | ax_code_coverage.m4 | 15 # coverage support. Also add rules using AX_ADD_AM_MACRO_STATIC; and
18 # value of the --enable-code-coverage option, which defaults to being
25 # coverage is enabled.
42 # clean-local: code-coverage-clean
43 # distclean-local: code-coverage-dist-clean
45 # This results in a "check-code-coverage" rule being added to any
47 # (assuming the module has been configured with --enable-code-coverage).
48 # Running `make check-code-coverage` in that directory will run the
49 # module's test suite (`make check`) and build a code coverage report
81 # Code coverage
[all …]
|
| /external/angle/build/android/docs/ |
| D | coverage.md | 1 # Android code coverage instructions
3 These are instructions for collecting code coverage data for android
4 instrumentation and JUnit tests. For Clang(C++) code coverage refer to [clang coverage].
8 ## How JaCoCo coverage works
10 In order to use JaCoCo code coverage, we need to create build time pre-instrumented
14 ## How to collect coverage data
25 2. Run tests, with option `--coverage-dir <directory>`, to specify where to save
27 `out/Debug/bin/run_chrome_junit_tests --coverage-dir /tmp/coverage`.
29 3. The coverage results of JUnit and instrumentation tests will be merged
32 ## How to generate coverage report
[all …]
|
| /external/cronet/build/android/docs/ |
| D | coverage.md | 1 # Android code coverage instructions
3 These are instructions for collecting code coverage data for android
4 instrumentation and JUnit tests. For Clang(C++) code coverage refer to [clang coverage].
8 ## How JaCoCo coverage works
10 In order to use JaCoCo code coverage, we need to create build time pre-instrumented
14 ## How to collect coverage data
25 2. Run tests, with option `--coverage-dir <directory>`, to specify where to save
27 `out/Debug/bin/run_chrome_junit_tests --coverage-dir /tmp/coverage`.
29 3. The coverage results of JUnit and instrumentation tests will be merged
32 ## How to generate coverage report
[all …]
|
| /external/fonttools/Tests/feaLib/data/ |
| D | lookupflag.ttx | 23 <Coverage index="0">
27 </Coverage>
28 <Coverage index="1">
34 </Coverage>
35 <Coverage index="2">
39 </Coverage>
116 <Coverage>
118 </Coverage>
128 <Coverage>
130 </Coverage>
[all …]
|
| /external/compiler-rt/test/ubsan/TestCases/Misc/ |
| D | coverage-levels.cc | 1 // Test various levels of coverage
6 // RUN: rm -rf %T/coverage-levels && mkdir %T/coverage-levels
7 // RUN: %clangxx -fsanitize=shift -DGOOD_SHIFT=1 -O1 -fsanitize-coverage=fun…
8 // RUN: %env_ubsan_opts=coverage=1:verbosity=1:coverage_dir='"%T/coverage-levels"' %run %t 2>&1 | F…
9 // RUN: %clangxx -fsanitize=undefined -DGOOD_SHIFT=1 -O1 -fsanitize-coverage=fun…
10 // RUN: %env_ubsan_opts=coverage=1:verbosity=1:coverage_dir='"%T/coverage-levels"' %run %t 2>&1 | F…
13 // RUN: %clangxx -DGOOD_SHIFT=1 -O1 -fsanitize-coverage=fun…
14 // RUN: %env_ubsan_opts=coverage=1:verbosity=1:coverage_dir='"%T/coverage-levels"' %run %t 2>&1 | F…
16 // RUN: %clangxx -fsanitize=shift -O1 -fsanitize-coverage=func %s -o %t
17 // RUN: %env_ubsan_opts=coverage=1:verbosity=1:coverage_dir='"%T/coverage-levels"' %run %t 2>&1 | F…
[all …]
|
| /external/pdfium/docs/ |
| D | code-coverage.md | 1 # Code Coverage Support for PDFium
5 This guide explains how to generate code coverage information for the PDFium
13 The tools used for code coverage are known to work on Ubuntu and Debian. They
17 Previously, the code coverage scripts required specific versions of `lcov` and
22 ## Generating Code Coverage
29 Before generating code coverage information, you will need to have a build
30 directory with coverage enabled. This can be done by running the `gn args`
33 If not using the default directory, `out/Coverage`, then replace it with the
37 gn args out/Coverage
40 If you already have a build directory, you can append the coverage flag to the
[all …]
|
| /external/jacoco/org.jacoco.ant.test/src/org/jacoco/ant/ |
| D | CoverageTaskTest.xml | 15 <project name="JaCoCo Coverage Task Tests" xmlns:au="antlib:org.apache.ant.antunit" xmlns:jacoco="a…
28 <au:expectfailure expectedMessage="A child task must be supplied for the coverage task">
29 <jacoco:coverage/>
35 <jacoco:coverage>
42 </jacoco:coverage>
49 <au:expectfailure expectedMessage="jar is not a valid child of the coverage task">
50 <jacoco:coverage>
52 </jacoco:coverage>
57 <jacoco:coverage destfile="${exec.file}">
61 </jacoco:coverage>
[all …]
|
| /external/harfbuzz_ng/m4/ |
| D | ax_code_coverage.m4 | 15 # coverage support. Also defines CODE_COVERAGE_RULES which should be
19 # --enable-code-coverage option, which defaults to being disabled.
25 # coverage is enabled.
41 # This results in a "check-code-coverage" rule being added to any
43 # has been configured with --enable-code-coverage). Running `make
44 # check-code-coverage` in that directory will run the module's test suite
45 # (`make check`) and build a code coverage report detailing the code which
81 dnl Check for --enable-code-coverage
86 [AS_HELP_STRING([--with-gcov[=GCOV]], [use given GCOV for coverage (GCOV=gcov).])],
90 AC_MSG_CHECKING([whether to build with code coverage support])
[all …]
|
| /external/strace/m4/ |
| D | ax_code_coverage.m4 | 15 # coverage support. Also defines CODE_COVERAGE_RULES which should be
19 # --enable-code-coverage option, which defaults to being disabled.
25 # coverage is enabled.
41 # This results in a "check-code-coverage" rule being added to any
43 # has been configured with --enable-code-coverage). Running `make
44 # check-code-coverage` in that directory will run the module's test suite
45 # (`make check`) and build a code coverage report detailing the code which
83 dnl Check for --enable-code-coverage
88 [AS_HELP_STRING([--with-gcov[=GCOV]], [use given GCOV for coverage (GCOV=gcov).])],
92 AC_MSG_CHECKING([whether to build with code coverage support])
[all …]
|
| /external/clang/docs/ |
| D | SanitizerCoverage.rst | 11 Sanitizer tools have a very simple code coverage tool built in. It allows to
12 get function-level, basic-block-level, and edge-level coverage at a very low
23 * ``-fsanitize-coverage=func`` for function-level coverage (very fast).
24 * ``-fsanitize-coverage=bb`` for basic-block-level coverage (may add up to 30%
26 * ``-fsanitize-coverage=edge`` for edge-level coverage (up to 40% slowdown).
28 You may also specify ``-fsanitize-coverage=indirect-calls`` for
29 additional `caller-callee coverage`_.
31 At run time, pass ``coverage=1`` in ``ASAN_OPTIONS``,
33 appropriate. For the standalone coverage mode, use ``UBSAN_OPTIONS``.
35 To get `Coverage counters`_, add ``-fsanitize-coverage=8bit-counters``
[all …]
|
| /external/oss-fuzz/infra/cifuzz/ |
| D | get_coverage.py | 14 """Module for determining coverage of fuzz targets."""
27 OSS_FUZZ_LATEST_COVERAGE_INFO_PATH = 'oss-fuzz-coverage/latest_report_info/'
32 """Exceptions for project coverage."""
36 """Gets coverage data for a project."""
45 target: The name of the fuzz target whose coverage is requested.
52 logging.info('No coverage available for %s', target)
57 logging.info('No files found in coverage report.')
79 """Get the coverage report for a specific fuzz target.
82 target: The name of the fuzz target whose coverage is requested.
85 The target's coverage json dict or None on failure.
[all …]
|
| /external/bazelbuild-rules_python/python/private/ |
| D | coverage_deps.bzl | 15 """Dependencies for coverage.py used by the hermetic toolchain.
26 …ages/3d/80/7060a445e1d2c9744b683dc935248613355657809d6c6b2716cdf4ca4766/coverage-7.2.7-cp310-cp310…
30 …ages/b8/9d/926fce7e03dbfc653104c2d981c0fa71f0572a9ebd344d24c573bd6f7c4f/coverage-7.2.7-cp310-cp310…
34 …ages/01/24/be01e62a7bce89bcffe04729c540382caa5a06bee45ae42136c93e2499f5/coverage-7.2.7-cp310-cp310…
38 …ages/b4/bd/1b2331e3a04f4cc9b7b332b1dd0f3a1261dfc4114f8479bebfcc2afee9e8/coverage-7.2.7-cp310-cp310…
44 …ages/67/d7/cd8fe689b5743fffac516597a1222834c42b80686b99f5b44ef43ccc2a43/coverage-7.2.7-cp311-cp311…
48 …ages/8c/95/16eed713202406ca0a37f8ac259bbf144c9d24f9b8097a8e6ead61da2dbb/coverage-7.2.7-cp311-cp311…
52 …ages/c6/fa/529f55c9a1029c840bcc9109d5a15ff00478b7ff550a1ae361f8745f8ad5/coverage-7.2.7-cp311-cp311…
56 …ages/a7/cd/3ce94ad9d407a052dc2a74fbeb1c7947f442155b28264eb467ee78dea812/coverage-7.2.7-cp311-cp311…
62 …ages/28/d7/9a8de57d87f4bbc6f9a6a5ded1eaac88a89bf71369bb935dac3c0cf2893e/coverage-7.2.7-cp38-cp38-m…
[all …]
|
| /external/google-cloud-java/java-dialogflow-cx/proto-google-cloud-dialogflow-cx-v3/src/main/java/com/google/cloud/dialogflow/cx/v3/ |
| D | TransitionRouteGroupCoverage.java | 25 * Transition route group coverage represents the percentage of all possible
74 …ertion_point(interface_extends:google.cloud.dialogflow.cx.v3.TransitionRouteGroupCoverage.Coverage)
116 * The list of transition routes and coverage in the transition route group.
120 …* repeated .google.cloud.dialogflow.cx.v3.TransitionRouteGroupCoverage.Coverage.Transition transit…
124 com.google.cloud.dialogflow.cx.v3.TransitionRouteGroupCoverage.Coverage.Transition>
130 * The list of transition routes and coverage in the transition route group.
134 …* repeated .google.cloud.dialogflow.cx.v3.TransitionRouteGroupCoverage.Coverage.Transition transit…
137 com.google.cloud.dialogflow.cx.v3.TransitionRouteGroupCoverage.Coverage.Transition
143 * The list of transition routes and coverage in the transition route group.
147 …* repeated .google.cloud.dialogflow.cx.v3.TransitionRouteGroupCoverage.Coverage.Transition transit…
[all …]
|
| /external/google-cloud-java/java-dialogflow-cx/proto-google-cloud-dialogflow-cx-v3beta1/src/main/java/com/google/cloud/dialogflow/cx/v3beta1/ |
| D | TransitionRouteGroupCoverage.java | 25 * Transition route group coverage represents the percentage of all possible
74 …n_point(interface_extends:google.cloud.dialogflow.cx.v3beta1.TransitionRouteGroupCoverage.Coverage)
116 * The list of transition routes and coverage in the transition route group.
120 …* repeated .google.cloud.dialogflow.cx.v3beta1.TransitionRouteGroupCoverage.Coverage.Transition tr…
124 com.google.cloud.dialogflow.cx.v3beta1.TransitionRouteGroupCoverage.Coverage.Transition>
130 * The list of transition routes and coverage in the transition route group.
134 …* repeated .google.cloud.dialogflow.cx.v3beta1.TransitionRouteGroupCoverage.Coverage.Transition tr…
137 com.google.cloud.dialogflow.cx.v3beta1.TransitionRouteGroupCoverage.Coverage.Transition
143 * The list of transition routes and coverage in the transition route group.
147 …* repeated .google.cloud.dialogflow.cx.v3beta1.TransitionRouteGroupCoverage.Coverage.Transition tr…
[all …]
|
| /external/rust/crates/libz-sys/src/zlib-ng/cmake/ |
| D | detect-coverage.cmake | 1 # detect-coverage.cmake -- Detect supported compiler coverage flags
5 # Check for -coverage flag support for Clang/GCC
9 set(CMAKE_REQUIRED_LINK_OPTIONS -coverage)
11 check_c_compiler_flag(-coverage HAVE_COVERAGE)
16 add_compile_options(-coverage)
17 add_link_options(-coverage)
18 message(STATUS "Code coverage enabled using: -coverage")
20 # Some versions of GCC don't support -coverage shorthand
26 check_c_compiler_flag("-ftest-coverage -fprofile-arcs -fprofile-values" HAVE_TEST_COVERAGE)
31 add_compile_options(-ftest-coverage -fprofile-arcs -fprofile-values)
[all …]
|
| /external/llvm/docs/CommandGuide/ |
| D | llvm-cov.rst | 1 llvm-cov - emit coverage information
12 The :program:`llvm-cov` tool shows code coverage information for
14 work with ``gcov``\-style coverage or with ``clang``\'s instrumentation
43 The :program:`llvm-cov gcov` tool reads code coverage data files and displays
44 the coverage information for a specified source file. It is compatible with the
49 of your application that collects coverage data as it runs. Compile with the
50 ``-fprofile-arcs`` and ``-ftest-coverage`` options to add the
51 instrumentation. (Alternatively, you can use the ``--coverage`` option, which
54 coverage data cannot be accurately mapped back to the source code.
58 coverage data. The other half of the data comes from ``.gcda`` files that are
[all …]
|
| /external/freetype/src/autofit/ |
| D | afcover.h | 20 /* Define `COVERAGE' as needed. */
24 /* coverage name in lowercase and uppercase, respectively, followed */
30 COVERAGE( alternative_fractions, ALTERNATIVE_FRACTIONS,
35 COVERAGE( petite_capitals_from_capitals, PETITE_CAPITALS_FROM_CAPITALS,
39 COVERAGE( small_capitals_from_capitals, SMALL_CAPITALS_FROM_CAPITALS,
44 /* XXX: Only digits are in this coverage, however, both normal style */
46 COVERAGE( denominators, DENOMINATORS,
53 COVERAGE( fractions, FRACTIONS,
59 /* XXX: Only digits are in this coverage, however, both normal style */
61 COVERAGE( numerators, NUMERATORS,
[all …]
|
| /external/swiftshader/tests/regres/cov/ |
| D | coverage_test.go | 26 fileA = "coverage/file/a"
27 fileB = "coverage/file/b"
28 fileC = "coverage/file/c"
29 fileD = "coverage/file/c"
51 t.Log("Add 'b' with the coverage [0,1]")
52 tree.Add(cov.Path{"a", "b"}, coverage(fileA, span0, span1))
63 t.Log("Add 'i' with the coverage [0,1]")
64 tree.Add(cov.Path{"a", "b", "d", "i"}, coverage(fileA, span0, span1))
78 t.Log("Add 'e' with the coverage [0,1,2]")
79 tree.Add(cov.Path{"a", "b", "e"}, coverage(fileA, span0, span1, span2))
[all …]
|
| /external/oss-fuzz/docs/advanced-topics/ |
| D | code_coverage.md | 3 title: Code coverage
6 permalink: /advanced-topics/code-coverage/
9 # Code Coverage
13 you can generate code coverage reports using Clang source-based code coverage.
15 For more details on C/C++ coverage, see [Clang's documentation].
17 Code coverage reports generation for other languages is not supported yet.
35 Code coverage report generation requires a special build configuration to be
36 used. To create a code coverage build for your project, run these commands:
40 $ python infra/helper.py build_fuzzers --sanitizer=coverage $PROJECT_NAME
46 coverage reports by running fuzz targets against the corpus
[all …]
|
12345678910>>...197