Searched +refs:clang +refs:format +refs:executable (Results 1 – 25 of 150) sorted by relevance
123456
| /external/bazelbuild-rules_rust/bindgen/private/ |
| D | bindgen.bzl | 33 """find the libraries used for linking a static executable. 60 …bindgen_flags (list, optional): Flags to pass directly to the bindgen executable. See https://rust… 62 clang_flags (list, optional): Flags to pass directly to the clang executable. 128 rustc_flags.append("-lstatic={}".format(get_lib_name_default(lib.static_library))) 132 … rustc_flags.append("-lstatic={}".format(get_lib_name_default(lib.pic_static_library))) 137 fail("No static libraries found in {}".format( 141 rustc_flags_file = ctx.actions.declare_file("{}.rustc_flags".format(ctx.label.name)) 147 link_search_paths = ctx.actions.declare_file("{}.link_search_paths".format(ctx.label.name)) 151 "-Lnative=${{pwd}}/{}".format(path) 173 … fail("Header {} is not in {}'s transitive headers.".format(ctx.attr.header, cc_lib), "header") [all …]
|
| /external/jazzer-api/ |
| D | WORKSPACE.bazel | 105 executable = True, 232 name = "clang-format-15-darwin-x64", 233 downloaded_file_path = "clang-format", 234 executable = True, 237 "https://github.com/angular/clang-format/raw/master/bin/darwin_x64/clang-format", 242 name = "clang-format-15-linux-x64", 243 downloaded_file_path = "clang-format", 244 executable = True, 247 "https://github.com/angular/clang-format/raw/master/bin/linux_x64/clang-format", 254 executable = True, [all …]
|
| /external/sandboxed-api/sandboxed_api/bazel/ |
| D | llvm_config.bzl | 26 "llvm-project-include/clang-c/**/*.h", 27 "llvm-project-include/clang/**/*.def", 28 "llvm-project-include/clang/**/*.h", 29 "llvm-project-include/clang/**/*.inc", 44 visibility = ["@llvm-project//clang:__pkg__"], 55 cc_library(name = "format", deps = ["@llvm-project//llvm:llvm"]) 68 "/usr/lib/llvm-{}/include/llvm/Support/InitLLVM.h".format(ver) 76 for suffix in ["llvm", "llvm-c", "clang", "clang-c"]: 98 lib_strs = sorted(["\"-l{}\",".format(a[5:-2]) for a in archives]) 106 ctx.file("clang/BUILD.bazel", SYSTEM_CLANG_BAZEL) [all …]
|
| D | sapi.bzl | 31 arguments.append("{}".format(name)) 47 executable = True, 53 return ctx.executable._generator_v1 54 return ctx.executable._generator_v2 149 extra_flags += ["--extra-arg=-D{}".format(d) for d in cc_ctx.defines.to_list()] 150 … extra_flags += ["--extra-arg=-isystem{}".format(i) for i in cc_ctx.system_includes.to_list()] 151 extra_flags += ["--extra-arg=-iquote{}".format(i) for i in quote_includes] 152 …extra_flags += ["--extra-arg=-isystem{}".format(d) for d in cpp_toolchain.built_in_include_directo… 180 "").format(ctx.outputs.out.short_path, len(input_files_paths)) 187 executable = generator, [all …]
|
| /external/skia/ |
| D | .clang-format | 3 # 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/ |
| D | README.md | 25 `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/ |
| D | CHANGELOG.md | 4 - Added support for `clang` 17.0.x 36 - Added additional support for `clang` 16.0.x 47 - Added support for `clang` 16.0.x 48 - Added support for `clang` 15.0.x 49 - Added support for `clang` 14.0.x 54 - Fixed `Clang::find` to check that `CLANG_PATH` is an executable file before 70 - Added support for `clang` 13.0.x 71 - Added support for `clang` 12.0.x 95 `x86_64-unknown-linux-gnu` are provided, a target-prefixed Clang executable 96 such as `x86_64-unknown-linux-gnu-clang` will be preferred over a non-target [all …]
|
| /external/cronet/build/apple/ |
| D | apple_info_plist.gni | 17 # 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/ |
| D | apple_info_plist.gni | 17 # 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/ |
| D | README.md | 52 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/pigweed/pw_toolchain_bazel/cc_toolchain/private/ |
| D | action_config.bzl | 31 exe = info.files_to_run.executable 43 exe = ctx.executable.tool or None 97 executable = True, 104 @llvm_toolchain//:bin/clang 110 * `bin/clang` is the path of the actual binary relative to the BUILD file of 127 tool = "@llvm_toolchain//:bin/clang", 133 path = "/usr/bin/clang", 172 fail("{} listed as a flag set to apply to {}, but none of the actions match".format( 179 exe = tool[DefaultInfo].files_to_run.executable 292 name = "clang",
|
| /external/bazelbuild-rules_go/go/private/actions/ |
| D | link.bzl | 38 return "{}={}={}".format(d.label, d.importmap, d.file.path) 58 …print("Multiple copies of {} passed to the linker. Ignoring {} in favor of {}".format(d.importmap,… 67 executable = None, 75 if executable == None: 76 fail("executable is a required parameter") 117 # (clang-15.0.3): 146 for f in rpath.flags(go, d, executable = executable) 174 builder_args.add("-o", executable) 207 outputs = [executable], 209 executable = go.toolchain._builder, [all …]
|
| /external/jsoncpp/ |
| D | CONTRIBUTING.md | 48 `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/bazelbuild-rules_cc/cc/ |
| D | system_library.bzl | 28 .format(assignment, var_name), 56 clang = _execute_bash(repo_ctx, "which clang++") 59 elif clang: 60 return clang 88 """.format( 116 """.format(compiler) 124 """.format(dir = directory, hdr = header_name) 154 fail("Library {} could not be found".format(repo_name)) 165 fail("Could not find required header {}".format(hdr)) 174 hdrs_param = "hdrs = {},".format(str(hdr_names)) [all …]
|
| /external/clang/docs/ |
| D | SourceBasedCodeCoverage.rst | 11 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
|
| D | AddressSanitizer.rst | 32 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
|
| D | UsersManual.rst | 16 `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/ |
| D | README.md | 41 …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/libaom/ |
| D | README.md | 52 3. A modern C compiler. gcc 6+, clang 7+, Microsoft Visual Studio 2019+ or 168 - arm64-linux-clang.cmake 534 The coding style used by this project is enforced with clang-format using the 536 [.clang-format](https://chromium.googlesource.com/webm/aom/+/main/.clang-format) 539 You can download clang-format using your system's package manager, or directly 541 [documentation](https://clang.llvm.org/docs/ClangFormat.html) on llvm.org. 542 Output from clang-format varies by clang-format version, for best results your 543 version should match the one used on Jenkins. You can find the clang-format 544 version by reading the comment in the `.clang-format` file linked above. 546 Before pushing changes for review you can format your code with: [all …]
|
| /external/clang/docs/CommandGuide/ |
| D | clang.rst | 1 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/deqp-deps/SPIRV-Tools/ |
| D | README.md | 176 * Combine into a library (exports are retained) or an executable (no symbols 222 The diff tool takes two SPIR-V files, either in binary or text format and 271 * Code should be formatted with `clang-format`. 272 [kokoro/check-format/build.sh](kokoro/check-format/build.sh) 274 `clang-format version 5.0.0` for SPIRV-Tools. Settings are defined by 275 the included [.clang-format](.clang-format) file. 463 platforms with an appropriate version of `clang` this option enables the use 464 of the sanitizers documented [here][clang-sanitizers]. 562 The standalone assembler is the executable called `spirv-as`, and is located in 575 The standalone disassembler is the executable called `spirv-dis`, and is located in [all …]
|
| /external/angle/third_party/spirv-tools/src/ |
| D | README.md | 180 * Combine into a library (exports are retained) or an executable (no symbols 226 The diff tool takes two SPIR-V files, either in binary or text format and 275 * Code should be formatted with `clang-format`. 276 [kokoro/check-format/build.sh](kokoro/check-format/build.sh) 278 `clang-format version 5.0.0` for SPIRV-Tools. Settings are defined by 279 the included [.clang-format](.clang-format) file. 467 platforms with an appropriate version of `clang` this option enables the use 468 of the sanitizers documented [here][clang-sanitizers]. 566 The standalone assembler is the executable called `spirv-as`, and is located in 579 The standalone disassembler is the executable called `spirv-dis`, and is located in [all …]
|
| /external/swiftshader/third_party/SPIRV-Tools/ |
| D | README.md | 180 * Combine into a library (exports are retained) or an executable (no symbols 226 The diff tool takes two SPIR-V files, either in binary or text format and 275 * Code should be formatted with `clang-format`. 276 [kokoro/check-format/build.sh](kokoro/check-format/build.sh) 278 `clang-format version 5.0.0` for SPIRV-Tools. Settings are defined by 279 the included [.clang-format](.clang-format) file. 467 platforms with an appropriate version of `clang` this option enables the use 468 of the sanitizers documented [here][clang-sanitizers]. 566 The standalone assembler is the executable called `spirv-as`, and is located in 579 The standalone disassembler is the executable called `spirv-dis`, and is located in [all …]
|
| /external/perfetto/docs/contributing/ |
| D | build-instructions.md | 169 We use `eslint` to lint TypeScript and JavaScript, and `prettier` to format 180 To auto-format all source files, run: 214 - Hermetic clang + libcxx toolchain (both following chromium's revisions) 221 - AOSP's in-tree clang (using in-tree libcxx) 225 - XCode 9 / clang (maintained best-effort). 229 - Windows 10 with either MSVC 2019 or clang-cl (maintained best-effort). 234 need the full IDE, just the build tools) or the LLVM clang-cl compiler. 239 clang-cl support is more stable because that build configuration is actively 259 You need all of these both for MSVC and clang-cl: 273 # This will download also the LLVM clang-cl prebuilt used by chromium. [all …]
|
| /external/vixl/ |
| D | README.md | 64 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`,
|
123456