| /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/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/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/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/rust/crates/grpcio-sys/grpc/third_party/cares/cares/m4/ |
| D | ax_code_coverage.m4 | 13 # (program or library) which should be built with code coverage support.
17 # corresponds to the value of the --enable-code-coverage option, which
24 # coverage is enabled.
38 # This results in a "check-code-coverage" rule being added to any
40 # has been configured with --enable-code-coverage). Running `make
41 # check-code-coverage` in that directory will run the module's test suite
42 # (`make check`) and build a code coverage report detailing the code which
73 dnl Check for --enable-code-coverage
78 [AS_HELP_STRING([--with-gcov[=GCOV]], [use given GCOV for coverage (GCOV=gcov).])],
82 AC_MSG_CHECKING([whether to build with code coverage support])
[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/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/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/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/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/openthread/third_party/nlbuild-autotools/repo/automake/post/rules/ |
| D | coverage.am | 20 # This file is the automake footer for all code-coverage related
24 # (automake in particular) such that 'make coverage' may be invoked
32 # coverage:
33 # Execute local and recursive coverage targets across the
38 # coverage-local:
39 # Execute local coverage targets at the current invocation point.
43 # coverage-recursive:
44 # Recursively execute the 'coverage' target across the
51 # targets at the current invocation point. Local coverage targets
53 # coverage targets are made.
[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/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/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/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/catch2/CMake/ |
| D | Findcodecov.cmake | 12 # Add an option to choose, if coverage should be enabled or not. If enabled
13 # marked targets will be build with coverage support and appropriate targets
14 # will be added. If disabled coverage will be ignored for *ALL* targets.
15 option(ENABLE_COVERAGE "Enable coverage build." OFF)
19 "-O0 -g -fprofile-arcs -ftest-coverage"
22 "-O0 -g --coverage"
26 # Add coverage support for target ${TNAME} and register target for coverage
27 # evaluation. If coverage is disabled or not supported, this function will
31 # coverage is not supported by the compiler or disabled. This function must
32 # be defined here, because the module will be exited, if there is no coverage
[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/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 …]
|
| /external/swiftshader/tests/regres/deqp/ |
| D | deqp.go | 65 TempDir string // Directory for temporary log files, coverage output.
82 Coverage *cov.Tree member
92 Coverage *cov.Coverage member
233 out.Coverage = &cov.Tree{}
234 out.Coverage.Add(cov.Path{}, c.CoverageEnv.AllSourceFiles())
252 if r.Coverage != nil {
254 out.Coverage.Add(cov.Path(path), r.Coverage)
255 r.Coverage = nil // Free memory
277 …// If you compile SwiftShader with gcc and the --coverage flag, the build will contain coverage in…
278 // We can use this to get the code coverage of SwiftShader from running dEQP.
[all …]
|
| /external/harfbuzz_ng/src/OT/Layout/GSUB/ |
| D | LigatureSubstFormat1.hh | 16 typename Types::template OffsetTo<Coverage>
17 coverage; /* Offset to Coverage table--from member
21 * ordered by Coverage Index */
28 return_trace (coverage.sanitize (c, this) && ligatureSet.sanitize (c, this)); in sanitize()
34 + hb_zip (this+coverage, ligatureSet) in intersects()
48 + hb_zip (this+coverage, ligatureSet) in closure()
61 if (unlikely (!(this+coverage).collect_coverage (c->input))) return; in collect_glyphs()
63 + hb_zip (this+coverage, ligatureSet) in collect_glyphs()
70 const Coverage &get_coverage () const { return this+coverage; } in get_coverage()
74 unsigned int index = (this+coverage).get_coverage (c->glyphs[0]); in would_apply()
[all …]
|
| /external/compiler-rt/test/asan/TestCases/Linux/ |
| D | coverage-missing.cc | 3 // First case: coverage from executable. main() is called on every code path.
4 // RUN: %clangxx_asan -fsanitize-coverage=func %s -o %t -DFOOBAR -DMAIN
5 // RUN: rm -rf %T/coverage-missing
6 // RUN: mkdir -p %T/coverage-missing
7 // RUN: cd %T/coverage-missing
8 // RUN: %env_asan_opts=coverage=1:coverage_dir=%T/coverage-missing %run %t
12 // RUN: %env_asan_opts=coverage=1:coverage_dir=%T/coverage-missing %run %t x
16 // RUN: %env_asan_opts=coverage=1:coverage_dir=%T/coverage-missing %run %t x x
27 // Second case: coverage from DSO.
29 // RUN: %clangxx_asan -fsanitize-coverage=func %s -o %dynamiclib -DFOOBAR -shared -fPIC
[all …]
|