Home
last modified time | relevance | path

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

123456

/external/skia/
D.clang-format3 # change. Make sure to install git-clang-format [1] by adding it to your
4 # path and make it executable.
7 # $ git clang-format
13 # Some clients are running on older versions of clang-format, so please limit
14 # flag choices to options supported by clang-format version 10 and below.
15 # - XcodeClangFormat: clang-format 10
16 # - bin/clang-format: clang-format 11
17 # - brew: clang-format 14
19 # [1] https://raw.githubusercontent.com/llvm-mirror/clang/master/tools/clang-format/git-clang-format
/external/openscreen/
DREADME.md25 `git cl format`, `git cl lint`, and `git cl upload.`
63 - Code formatter: `clang-format`
65 - Compiler/Linker: `clang` (installed by default) or `gcc` (installed by you)
73 `clang-format` is used for maintaining consistent coding style, but it is not a
78 ## Linux clang
83 Ensure that libstdc++ 8 is installed, as clang depends on the system
107 ## Mac clang
109 On Mac OS X, the build will use the clang provided by
149 ninja -C out/debug osp_demo # Builds the executable with ninja
150 ./out/debug/osp_demo # Runs the executable
[all …]
/external/rust/crates/clang-sys/
DCHANGELOG.md10 - Added support for `clang` 16.0.x
11 - Added support for `clang` 15.0.x
12 - Added support for `clang` 14.0.x
17 - Fixed `Clang::find` to check that `CLANG_PATH` is an executable file before
33 - Added support for `clang` 13.0.x
34 - Added support for `clang` 12.0.x
58 `x86_64-unknown-linux-gnu` are provided, a target-prefixed Clang executable
59 such as `x86_64-unknown-linux-gnu-clang` will be preferred over a non-target
60 prefixed Clang executable)
76 ([#121](https://github.com/KyleMayes/clang-sys/issues/121))
[all …]
/external/cronet/build/apple/
Dapple_info_plist.gni17 # and executable name as specified in the output Info.plist.
19 # format:
20 # string, the format to `plutil -convert` the plist to when
42 "format",
53 "GCC_VERSION=com.apple.compilers.llvm.clang.1_0",
/external/angle/build/apple/
Dapple_info_plist.gni17 # and executable name as specified in the output Info.plist.
19 # format:
20 # string, the format to `plutil -convert` the plist to when
42 "format",
53 "GCC_VERSION=com.apple.compilers.llvm.clang.1_0",
/external/OpenCL-CTS/
DREADME.md52 See the `--help` output on each executable for the list of sub-tests available,
84 * `--compilation-program` Accepts a path to an executable (default:
86 compilation of OpenCL-C source code. This executable must match the
112 PRs to the repository are required to be `clang-format` clean to pass CI.
113 Developers can either use the `git-clang-format` tool locally to verify this
/external/jsoncpp/
DCONTRIBUTING.md48 `jsontest` executable that was compiled on your platform.
79 * a `TESTNAME.json` file, that contains the input document in JSON format.
83 The `TESTNAME.expected` file format is as follows:
146 …e modifying (or the above rules for new files), and run clang format. Meson exposes clang format w…
148 ninja -v -C build-${LIB_TYPE}/ clang-format
/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
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 …]
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
/external/swiftshader/
DREADME.md41 …de to use SwiftShader's DLLs by placing them in the same folder as the executable. On Linux, the `…
72 …clang-format 11.0.1](tests/kokoro/gcp_ubuntu/check_style.sh). Most IDEs come with clang-format sup…
/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/swiftshader/third_party/SPIRV-Tools/
DREADME.md175 * Combine into a library (exports are retained) or an executable (no symbols
221 The diff tool takes two SPIR-V files, either in binary or text format and
270 * Code should be formatted with `clang-format`.
271 [kokoro/check-format/build.sh](kokoro/check-format/build.sh)
273 `clang-format version 5.0.0` for SPIRV-Tools. Settings are defined by
274 the included [.clang-format](.clang-format) file.
456 platforms with an appropriate version of `clang` this option enables the use
457 of the sanitizers documented [here][clang-sanitizers].
555 The standalone assembler is the executable called `spirv-as`, and is located in
568 The standalone disassembler is the executable called `spirv-dis`, and is located in
[all …]
/external/deqp-deps/SPIRV-Tools/
DREADME.md173 * Combine into a library (exports are retained) or an executable (no symbols
219 The diff tool takes two SPIR-V files, either in binary or text format and
268 * Code should be formatted with `clang-format`.
269 [kokoro/check-format/build.sh](kokoro/check-format/build.sh)
271 `clang-format version 5.0.0` for SPIRV-Tools. Settings are defined by
272 the included [.clang-format](.clang-format) file.
451 platforms with an appropriate version of `clang` this option enables the use
452 of the sanitizers documented [here][clang-sanitizers].
550 The standalone assembler is the executable called `spirv-as`, and is located in
563 The standalone disassembler is the executable called `spirv-dis`, and is located in
[all …]
/external/angle/third_party/vulkan-deps/spirv-tools/src/
DREADME.md175 * Combine into a library (exports are retained) or an executable (no symbols
221 The diff tool takes two SPIR-V files, either in binary or text format and
270 * Code should be formatted with `clang-format`.
271 [kokoro/check-format/build.sh](kokoro/check-format/build.sh)
273 `clang-format version 5.0.0` for SPIRV-Tools. Settings are defined by
274 the included [.clang-format](.clang-format) file.
462 platforms with an appropriate version of `clang` this option enables the use
463 of the sanitizers documented [here][clang-sanitizers].
561 The standalone assembler is the executable called `spirv-as`, and is located in
574 The standalone disassembler is the executable called `spirv-dis`, and is located in
[all …]
/external/libaom/
DREADME.md528 The coding style used by this project is enforced with clang-format using the
530 [.clang-format](https://chromium.googlesource.com/webm/aom/+/main/.clang-format)
533 You can download clang-format using your system's package manager, or directly
535 [documentation](https://clang.llvm.org/docs/ClangFormat.html) on llvm.org.
536 Output from clang-format varies by clang-format version, for best results your
537 version should match the one used on Jenkins. You can find the clang-format
538 version by reading the comment in the `.clang-format` file linked above.
540 Before pushing changes for review you can format your code with:
543 # Apply clang-format to modified .c, .h and .cc files
544 $ clang-format -i --style=file \
[all …]
/external/vixl/
DREADME.md64 3. clang-format-4.0
65 4. clang-tidy-4.0
69 Note that in Ubuntu 18.04, clang-tidy-4.0 will only work if the clang-4.0
228 executable) on the `PATH`.
234 Additionally, `tools/test.py` tests code formatting using `clang-format-4.0`,
235 and performs static analysis using `clang-tidy-4.0`. If you don't have these
236 tools, disable the test using `--noclang-format` or `--noclang-tidy`,
/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".
/external/cronet/third_party/boringssl/src/util/
DBUILD.toplevel48 # clang-assembler, on aarch64. We have not yet added NASM support to this build,
49 # and would need to detect MSVC vs clang-cl for aarch64 so, for now, we just
54 # we want OPENSSL_NO_ASM, in case the C files expect them in some format (e.g.
76 # ensure that binaries can be built with non-executable stack.
/external/boringssl/src/util/
DBUILD.toplevel48 # clang-assembler, on aarch64. We have not yet added NASM support to this build,
49 # and would need to detect MSVC vs clang-cl for aarch64 so, for now, we just
54 # we want OPENSSL_NO_ASM, in case the C files expect them in some format (e.g.
76 # ensure that binaries can be built with non-executable stack.
/external/boringssl/
DBUILD48 # clang-assembler, on aarch64. We have not yet added NASM support to this build,
49 # and would need to detect MSVC vs clang-cl for aarch64 so, for now, we just
54 # we want OPENSSL_NO_ASM, in case the C files expect them in some format (e.g.
76 # ensure that binaries can be built with non-executable stack.
/external/googletest/
DCONTRIBUTING.md82 [.clang-format](https://github.com/google/googletest/blob/master/.clang-format)
117 explicitly where your Python executable can be found:
/external/cronet/third_party/googletest/src/
DCONTRIBUTING.md83 [.clang-format](https://github.com/google/googletest/blob/master/.clang-format)
118 explicitly where your Python executable can be found:
/external/perfetto/docs/contributing/
Dbuild-instructions.md188 - Hermetic clang + libcxx toolchain (both following chromium's revisions)
195 - AOSP's in-tree clang (using in-tree libcxx)
199 - XCode 9 / clang (maintained best-effort).
203 - Windows 10 with either MSVC 2019 or clang-cl (maintained best-effort).
208 need the full IDE, just the build tools) or the LLVM clang-cl compiler.
213 clang-cl support is more stable because that build configuration is actively
233 You need all of these both for MSVC and clang-cl:
247 # This will download also the LLVM clang-cl prebuilt used by chromium.
262 is_clang = true # Will use the hermetic clang-cl toolchain.
335 On Linux, by default it uses the self-hosted clang (see `is_hermetic_clang`).
[all …]

123456