Home
last modified time | relevance | path

Searched +refs:clang +refs:format +refs:executable (Results 1 – 25 of 74) sorted by relevance

123

/external/webrtc/webrtc/modules/audio_coding/codecs/isac/
Disac_test.gypi14 'type': 'executable',
29 ['OS=="win" and clang==1', {
35 '-Wno-format',
45 'type': 'executable',
63 'type': 'executable',
/external/v8/tools/clang/traffic_annotation_extractor/
DREADME.md2 This is a clang tool to extract network traffic annotations. The tool is run by
7 `tools/clang/scripts/update.py --bootstrap --force-local-build
14 2. Run `python tools/clang/scripts/update.py --bootstrap --force-local-build
25 `tools/clang/scripts/run_tool.py --tool=traffic_annotation_extractor
28 The executable extracts network traffic annotations and calls to network request
35 Each annotation output will have the following format:
47 Each function call output will have the following format:
55 Each direct assignment output will have the following format:
/external/swiftshader/third_party/llvm-7.0/llvm/utils/lit/lit/llvm/
Dconfig.py185 def get_clang_builtin_include_dir(self, clang): argument
189 [clang, '-print-file-name=include'])
193 "Couldn't find the include dir for Clang ('%s')" % clang)
203 def get_clang_has_lsan(self, clang, triple): argument
204 if not clang:
209 clang_binary = clang.split()[0]
302 self.config.substitutions.append(('%python', '"%s"' % (sys.executable)))
322 message = "couldn't find '{}' program".format(name)
325 ', try setting {} in your environment'.format(search_env)
331 self.lit_config.note('using {}: {}'.format(name, tool))
[all …]
/external/clang/docs/
DSourceBasedCodeCoverage.rst11 This document explains how to use clang's source-based code coverage feature.
61 % clang++ -fprofile-instr-generate -fcoverage-mapping foo.cc -o foo
184 profile format. Raw profiles may be dependent on the specific compiler
189 These formats are not forwards-compatible: i.e, a tool which uses format
190 version X will not be able to understand format version (X+k).
192 * There is a third format in play: the format of the coverage mappings emitted
204 library and executable. When the linker finds a definition of this symbol, it
209 once from each instrumented executable. This function parses
DAddressSanitizer.rst32 AddressSanitizer run-time library should be linked to the final executable, so
33 make sure to use ``clang`` (not ``ld``) for the final link step. When linking
51 % clang -O1 -g -fsanitize=address -fno-omit-frame-pointer example_UseAfterFree.cc
58 % clang -O1 -g -fsanitize=address -fno-omit-frame-pointer -c example_UseAfterFree.cc
60 % clang -g -fsanitize=address example_UseAfterFree.o
76 executable. (You can find the library by searching for dynamic libraries with
78 try to re-exec. Also keep in mind that when moving the executable to another machine,
162 path of the file relative to the location of your executable.
168 Use the following format to specify the names of the functions or libraries
DSanitizerCoverage.rst53 % clang++ -g cov.cc -fsanitize=address -fsanitize-coverage=func
63 Every time you run an executable instrumented with SanitizerCoverage
65 If the executable is dynamically linked against instrumented DSOs,
71 The format of ``*.sancov`` files is very simple: the first 8 bytes is the magic,
120 -blacklist=<string> - Blacklist file (sanitizer blacklist format).
203 % clang++ -fsanitize=address -fsanitize-coverage=edge cov.cc
215 For a given executable the length of the bitset is always the same (well,
239 * The output format is not very compact since caller and callee may reside in
259 % clang++ -g cov.cc -fsanitize=address -fsanitize-coverage=edge,8bit-counters
299 % clang -g -fsanitize=address -fsanitize-coverage=edge,trace-bb foo.cc
DUsersManual.rst16 `Clang Web Site <http://clang.llvm.org>`_ or the `LLVM Web
23 `Clang Static Analyzer <http://clang-analyzer.llvm.org>`_, please see its web
47 Clang also provides an alternative driver, :ref:`clang-cl`, that is designed
154 output format of the diagnostics that it generates.
245 .. option:: -fdiagnostics-format=clang/msvc/vi
247 Changes diagnostic output format to better match IDEs and command line tools.
249 This option controls the output format of the filename, line number,
253 **clang** (default)
303 For example, a format string warning will produce these three
342 parsable format after the file/line/column number information. The
[all …]
/external/swiftshader/third_party/llvm-7.0/llvm/docs/
DCFIVerify.rst30 - Integration tests, present in "/llvm/tools/clang/test/LLVMCFIVerify". These
31 integration tests are part of clang as part of a continuous integration
57 This tool will disassemble binaries and DSO's from their machine code format and
85 Only machine code sections that are marked as executable will be subject to this
86 analysis. Non-executable sections do not require analysis as any execution
DGettingStartedVS.rst21 The second piece is the `Clang <http://clang.llvm.org/>`_ front end. This
24 machine code. LLVM fully supports the COFF object file format, which is
177 C:\..> clang -c hello.c -emit-llvm -o hello.bc
185 Alternatively you can directly output an executable with clang with:
189 C:\..> clang hello.c -o hello.exe
191 The ``-o hello.exe`` is required because clang currently outputs ``a.out``
/external/deqp-deps/SPIRV-Tools/
DREADME.md124 * Combine into a library (exports are retained) or an executable (no symbols
166 * Code should be formatted with `clang-format`.
167 [kokoro/check-format/build.sh](kokoro/check-format/build.sh)
169 `clang-format version 5.0.0` for SPIRV-Tools. Settings are defined by
170 the included [.clang-format](.clang-format) file.
267 platforms with an appropriate version of `clang` this option enables the use
268 of the sanitizers documented [here][clang-sanitizers].
371 The standalone disassembler is the executable called `spirv-dis`, and is located in
409 The standalone validator is the executable called `spirv-val`, and is located in
433 `spirv-dis` are on your executable search path:
[all …]
/external/swiftshader/third_party/SPIRV-Tools/
DREADME.md124 * Combine into a library (exports are retained) or an executable (no symbols
166 * Code should be formatted with `clang-format`.
167 [kokoro/check-format/build.sh](kokoro/check-format/build.sh)
169 `clang-format version 5.0.0` for SPIRV-Tools. Settings are defined by
170 the included [.clang-format](.clang-format) file.
267 platforms with an appropriate version of `clang` this option enables the use
268 of the sanitizers documented [here][clang-sanitizers].
371 The standalone disassembler is the executable called `spirv-dis`, and is located in
409 The standalone validator is the executable called `spirv-val`, and is located in
433 `spirv-dis` are on your executable search path:
[all …]
/external/vixl/
DREADME.md57 3. clang-format-3.8
148 executable) on the `PATH`.
154 Additionally, `tools/test.py` tests code formatting using `clang-format-3.8`.
155 If you don't have `clang-format-3.8`, disable the test using the
156 `--noclang-format` option.
/external/clang/docs/CommandGuide/
Dclang.rst1 clang - the Clang C, C++, and Objective-C compiler
7 :program:`clang` [*options*] *filename ...*
12 :program:`clang` is a C, C++, and Objective-C compiler which encompasses
20 The clang executable is actually a small driver which controls the overall
56 executable or dynamic library. The output of this stage is typically called
63 the same driver. Please see <http://clang-analyzer.llvm.org> for more details
92 linker is run to combine the results into an executable or shared library.
271 option transparently switches the Clang module format to object file
330 assembly files, otherwise this generates LLVM bitcode format object files
465 Do not search clang's builtin directory for include files.
/external/libaom/libaom/
DREADME.md486 The coding style used by this project is enforced with clang-format using the
488 [.clang-format](https://chromium.googlesource.com/webm/aom/+/master/.clang-format)
491 You can download clang-format using your system's package manager, or directly
493 [documentation](https://clang.llvm.org/docs/ClangFormat.html) on llvm.org.
494 Output from clang-format varies by clang-format version, for best results your
495 version should match the one used on Jenkins. You can find the clang-format
496 version by reading the comment in the `.clang-format` file linked above.
498 Before pushing changes for review you can format your code with:
501 # Apply clang-format to modified .c, .h and .cc files
502 $ clang-format -i --style=file \
[all …]
/external/llvm/docs/CommandGuide/
Dllvm-cov.rst14 work with ``gcov``\-style coverage or with ``clang``\'s instrumentation
84 count is shown as ``-`` if a line does not contain any executable code. If
180 ``clang`` use the ``-fprofile-instr-generate`` and ``-fcoverage-mapping``
181 flags. If linking with the ``clang`` driver, pass ``-fprofile-instr-generate``
184 The coverage information is stored in the built executable or library itself,
188 typically called ``default.profraw``, which can be converted to a format that
239 .. option:: -format=<FORMAT>
241 Use the specified output format. The supported formats are: "text", "html".
Dllc.rst14 through a native assembler and linker to generate a native executable.
25 language format (``.ll``) or the LLVM bitcode format (``.bc``).
48 :program:`clang`.
/external/swiftshader/third_party/llvm-7.0/llvm/docs/CommandGuide/
Dllvm-cov.rst14 work with ``gcov``\-style coverage or with ``clang``\'s instrumentation
85 count is shown as ``-`` if a line does not contain any executable code. If
181 ``clang`` use the ``-fprofile-instr-generate`` and ``-fcoverage-mapping``
182 flags. If linking with the ``clang`` driver, pass ``-fprofile-instr-generate``
185 The coverage information is stored in the built executable or library itself,
189 typically called ``default.profraw``, which can be converted to a format that
253 .. option:: -format=<FORMAT>
255 Use the specified output format. The supported formats are: "text", "html".
260 only supported for the html format.
400 `llvm-cov report` command, but presented in JSON format rather than text.
Dllc.rst14 through a native assembler and linker to generate a native executable.
25 language format (``.ll``) or the LLVM bitcode format (``.bc``).
48 :program:`clang`.
/external/python/cpython2/Mac/BuildScript/
DREADME.txt9 package from the now obsolete bundle-format installer package produced
24 using the newer flat package format, supported on 10.5+, and signed with the
102 produce a non-functional Python executable. As it appears to be
104 its use should be avoided. The other compiler, ``clang``, has been
165 ``i386``, ``x86_64``, ``ppc``, and ``ppc64`` (G5). ``ppc64`` executable
/external/llvm/docs/
DGettingStartedVS.rst21 The second piece is the `Clang <http://clang.llvm.org/>`_ front end. This
24 machine code. LLVM fully supports the COFF object file format, which is
170 C:\..> clang -c hello.c -emit-llvm -o hello.bc
178 Alternatively you can directly output an executable with clang with:
182 C:\..> clang hello.c -o hello.exe
184 The ``-o hello.exe`` is required because clang currently outputs ``a.out``
DLibFuzzer.rst42 git clone https://chromium.googlesource.com/chromium/src/tools/clang
44 TMP_CLANG/clang/scripts/update.py
47 ``./third_party/llvm-build/Release+Asserts/bin/clang``)
86 clang++ -c -g -O2 -std=c++11 Fuzzer/*.cpp -IFuzzer
92 the libFuzzer code then gives an fuzzer executable.
108clang -fsanitize-coverage=edge -fsanitize=address your_lib.cc fuzz_target.cc libFuzzer.a -o my_fuz…
382 clang++ -fsanitize=address -fsanitize-coverage=edge test_fuzzer.cc libFuzzer.a
410 …(cd pcre2-10.20; ./autogen.sh; CC="clang -fsanitize=address $COV_FLAGS" ./configure --prefix=`pwd`…
430 clang++ -g -fsanitize=address $COV_FLAGS -c -std=c++11 -I inst/include/ pcre_fuzzer.cc
432clang++ -g -fsanitize=address -Wl,--whole-archive inst/lib/*.a -Wl,-no-whole-archive libFuzzer.a p…
[all …]
/external/googletest/
DCONTRIBUTING.md82 Use [.clang-format](https://github.com/google/googletest/blob/master/.clang-format) to check your f…
115 executable can be found:
/external/swiftshader/third_party/LLVM/docs/CommandGuide/
Dllc.pod15 a native assembler and linker to generate a native executable.
25 format (.ll) or the LLVM bitcode format (.bc).
49 B<clang>.
/external/perfetto/gn/standalone/
DBUILD.gn25 # Disable Weverything on fuzzers to avoid breakages when new versions of clang
145 "-Wno-format-nonliteral",
218 config("executable") {
/external/tensorflow/tensorflow/compiler/aot/
Dcodegen_test_h.golden7 // clang-format off
32 // TensorFlow graph, now compiled into executable code. This extends the generic
331 // clang-format on

123