Searched +refs:clang +refs:format +refs:executable (Results 1 – 25 of 39) sorted by relevance
12
/external/webrtc/webrtc/modules/audio_coding/codecs/isac/ |
D | isac_test.gypi | 14 'type': 'executable', 29 ['OS=="win" and clang==1', { 35 '-Wno-format', 45 'type': 'executable', 63 'type': 'executable',
|
/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 …]
|
D | SanitizerCoverage.rst | 53 % 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/vixl/ |
D | README.md | 57 3. clang-format-3.6 148 executable) on the `PATH`. 154 Additionally, `tools/test.py` tests code formatting using `clang-format-3.6`. 155 If you don't have `clang-format-3.6`, disable the test using the 156 `--noclang-format` option.
|
/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/llvm/docs/CommandGuide/ |
D | llvm-cov.rst | 14 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".
|
D | llc.rst | 14 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/icu/icu4c/source/i18n/ |
D | Android.bp | 100 "format.cpp", 225 clang: true, 265 …cflags: ["-Os"], // Using -Os over -O3 actually cuts down the final executable size by a few dozen…
|
/external/llvm/docs/ |
D | GettingStartedVS.rst | 21 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``
|
D | LibFuzzer.rst | 42 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. 108 …clang -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 432 …clang++ -g -fsanitize=address -Wl,--whole-archive inst/lib/*.a -Wl,-no-whole-archive libFuzzer.a p… [all …]
|
D | CoverageMappingFormat.rst | 2 :format: html 14 LLVM's code coverage mapping format is used to provide code coverage 24 then we briefly desribe LLVM's code coverage mapping format and the 25 way that Clang and LLVM's code coverage tool work with this format. After 26 the basics are down, more advanced features of the coverage mapping format 40 ``clang -o test -fprofile-instr-generate -fcoverage-mapping test.c`` 56 LLVM's code coverage mapping format is designed to be a self contained 57 data format, that can be embedded into the LLVM IR and object files. 58 It's described in this document as a **mapping** format because its goal is 65 1. When clang compiles a source file with ``-fcoverage-mapping``, it [all …]
|
D | GettingStarted.rst | 20 The second piece is the `Clang <http://clang.llvm.org/>`_ front end. This 33 Getting Started <http://clang.llvm.org/get_started.html>`_ page might also be a 53 * ``svn co http://llvm.org/svn/llvm-project/cfe/trunk clang`` 519 If you want to check out clang too, run: 524 % git clone http://llvm.org/git/clang.git 587 But you may generate patchset with git-format-patch. It generates by-each-commit 592 % git format-patch --no-attach master..mybranch -o /path/to/your/patchset 599 % git format-patch --attach master..mybranch --stdout | git imap-send 633 # If you have clang too: 635 % git clone http://llvm.org/git/clang.git [all …]
|
/external/swiftshader/third_party/LLVM/docs/CommandGuide/ |
D | llc.pod | 15 a native assembler and linker to generate a native executable. 25 format (.ll) or the LLVM bitcode format (.bc). 49 B<clang>.
|
/external/fmtlib/ |
D | README.rst | 25 but still very fast, replacement-based `format API 26 <http://fmtlib.net/latest/api.html#format-api>`_ with positional arguments 30 * Format API with `format string syntax 32 similar to the one used by `str.format 33 <https://docs.python.org/2/library/stdtypes.html#str.format>`_ in Python. 38 * High speed: performance of the format API is close to that of 48 * Safety: the library is fully type safe, errors in format strings are 70 fmt::print("Hello, {}!", "world"); // uses Python-like format string syntax 71 fmt::printf("Hello, %s!", "world"); // uses printf format string syntax 77 std::string s = fmt::format("{0}{1}{0}", "abra", "cad"); [all …]
|
/external/skia/gn/ |
D | BUILD.gn | 14 cc = "$ndk/toolchains/llvm/prebuilt/$ndk_host/bin/clang.exe" 15 cxx = "$ndk/toolchains/llvm/prebuilt/$ndk_host/bin/clang++.exe" 18 cc = "$ndk/toolchains/llvm/prebuilt/$ndk_host/bin/clang" 19 cxx = "$ndk/toolchains/llvm/prebuilt/$ndk_host/bin/clang++" 49 is_clang = is_android || is_ios || is_mac || (cc == "clang" && cxx == "clang++") 357 "-Wno-format-nonliteral", 464 config("executable") {
|
/external/clang/include/clang/Driver/ |
D | CC1Options.td | 1 //===--- CC1Options.td - Options for clang -cc1 ---------------------------===// 10 // This file defines the options accepted by clang -cc1 and clang -cc1as. 143 HelpText<"Mark the file as not needing an executable stack">; 178 HelpText<"Generate debug info with external references to clang modules" 279 HelpText<"Enable PGO instrumentation. The accepted value is clang, llvm, " 312 HelpText<"File for serializing diagnostics in a binary format">; 314 def fdiagnostics_format : Separate<["-"], "fdiagnostics-format">, 412 def fmodule_format_EQ : Joined<["-"], "fmodule-format=">, 413 HelpText<"Select the container format for clang modules and PCH. " 552 HelpText<"File is for a position independent executable">;
|
/external/clang/include/clang/Basic/ |
D | Attr.td | 56 include "clang/Basic/AttrDocs.td" 64 include "clang/Basic/DeclNodes.td" 65 include "clang/Basic/StmtNodes.td" 433 CXX11<"clang", "xray_always_instrument">, 435 CXX11<"clang", "xray_never_instrument">]; 440 CXX11<"clang", "xray_always_instrument">]>, 443 CXX11<"clang", "xray_never_instrument">]>]; 537 // '#pragma clang arc_cf_code_audited' rather than explicitly. 799 CXX11<"clang", "fallthrough">]; 838 let Spellings = [GCC<"format">]; [all …]
|
/external/libpcap/ |
D | aclocal.m4 | 81 dnl that defines __GNUC__, which means clang, for example, counts as "gcc". 113 # This is assumed either to be GCC or clang, both 231 # We're assuming this is clang, where 308 # MIPS C for IRIX, DEC C, and clang all use -M. 346 # Note: clang doesn't seem to exit with an error status when handed 349 # -M, so the fact that this test always succeeds with clang 684 AC_MSG_WARN(ignoring obsolete flex executable ($s)) 1186 dnl Test whether __attribute__((format)) can be used without warnings 1190 AC_MSG_CHECKING([whether __attribute__((format)) can be used without warnings]) 1199 __attribute__ ((format (printf, 1, 2))); [all …]
|
/external/llvm/ |
D | CMakeLists.txt | 58 set(CMAKE_LIBTOOL ${CMAKE_LIBTOOL} CACHE PATH "libtool executable") 543 # LLVMBuild files in a format which is easy to consume from CMake, and will add 655 # when crosscompiling import the executable targets from a file 686 message(FATAL_ERROR "LLVM_PROFDATA_FILE can only be specified when compiling with clang") 760 if(EXISTS ${LLVM_MAIN_SRC_DIR}/projects/test-suite AND TARGET clang)
|
/external/llvm/docs/tutorial/ |
D | LangImpl09.rst | 19 source that the programmer wrote. In LLVM we generally use a format 147 our piece of Kaleidoscope language down to an executable program via this 152 Kaleidoscope-Ch9 < fib.ks | & clang -x ir - 452 …clang++ -g toy.cpp `llvm-config --cxxflags --ldflags --system-libs --libs core mcjit native` -O3 -…
|
/external/valgrind/ |
D | configure.ac | 120 # ######## clang variants ######## 121 # Clang: clang version 2.9 (tags/RELEASE_29/final) 122 # Apple clang: Apple clang version 3.1 (tags/Apple/clang-318.0.58) (based on LLVM 3.1svn) 123 # FreeBSD clang: FreeBSD clang version 3.1 (branches/release_31 156863) 20120523 126 # Apple LLVM version 5.1 (clang-503.0.40) (based on LLVM 3.4svn) 127 # Apple LLVM version 6.0 (clang-600.0.51) (based on LLVM 3.5svn) 130 if test "x`${CC} --version | $SED -n -e 's/.*\Apple \(LLVM\) version.*clang.*/\1/p'`" = "xLLVM" ; 134 elif test "x`${CC} --version | $SED -n -e 's/.*\(clang\) version.*/\1/p'`" = "xclang" ; 136 is_clang="clang" 137 # Don't use -dumpversion with clang: it will always produce "4.2.1". [all …]
|
D | NEWS | 207 will automatically load the executable file of the process running 208 under Valgrind. This means you do not need to specify the executable 294 342008 valgrind.h needs type cast [..] for clang/llvm in 64-bit mode 296 342063 wrong format specifier for test mcblocklistsearch in gdbserver_tests 327 343967 Don't warn about setuid/setgid/setcap executable for directories 399 348565 Fix detection of command line option availability for clang 403 348890 Fix clang warning about unsupported --param inline-unit-growth=900 750 329694 clang warns about using uninitialized variable 802 334727 Build fails with -Werror=format-security 1089 307955 Building valgrind 3.7.0-r4 fails in Gentoo AMD64 when using clang [all …]
|
/external/syslinux/gnu-efi/gnu-efi-3.0/ |
D | ChangeLog | 207 be hit. This also can break clang, which doesn't have a stdint-gcc.h at all. 219 @function. The clang compiler doesn't like the former. Clang and GCC both like 242 check. This prevents clang from inserting a call to memset() when compiling 255 - Allows GNU EFI to build out of the box with either GCC or clang on 344 executable failing to boot in a secure boot environment. 486 ELF image. ELILO autodetects the format
|
12