Searched +refs:clang +refs:format +refs:region (Results 1 – 14 of 14) sorted by relevance
| /external/clang/docs/ |
| D | ClangFormat.rst | 13 :program:`clang-format` is located in `clang/tools/clang-format` and can be used 14 to format C/C++/Obj-C code. 18 $ clang-format -help 19 OVERVIEW: A tool to format C/C++/Java/JavaScript/Objective-C/Protobuf code. 27 USAGE: clang-format [options] [<file> ...] 31 Clang-format options: 33 -assume-filename=<string> - When reading from stdin, clang-format assumes this 37 clang-format from an editor integration 41 fallback in case clang-format is invoked with 42 -style=file, but can not find the .clang-format [all …]
|
| D | AddressSanitizer.rst | 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 96 0x7f7ddab8c084 is located 4 bytes inside of 400-byte region [0x7f7ddab8c080,0x7f7ddab8c210) 168 Use the following format to specify the names of the functions or libraries
|
| /external/llvm/docs/ |
| 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 | ExceptionHandling.rst | 12 exception handling in LLVM. It describes the format that LLVM exception 36 exception frame format can be found at `Exception Frames 436 a destination address by `llvm.eh.sjlj.longjmp`_. The buffer format and the 438 ``__builtin_setjmp`` implementation allowing code built with the clang and GCC 502 The format of this call frame information (CFI) is often platform-dependent, 503 however. ARM, for example, defines their own format. Apple has their own compact 504 unwind info format. On Windows, another format is used for all architectures 513 referred to as the language-specific data area (LSDA). The format of the LSDA 592 if the exception came from a particular DLL or code region, or if code faulted
|
| D | LangRef.rst | 448 On targets that use the ELF object file format, default visibility 573 region of memory, and all memory objects in LLVM are accessed through 1133 have a particular format. Specifically, it must begin with a sequence of 1139 makes the format of the prologue data highly target dependent. 1379 `SafeStack <http://clang.llvm.org/docs/SafeStack.html>`_ 2528 values are represented in their IEEE hexadecimal format so that assembly 2535 precision, respectively. Hexadecimal format is always used for long 2536 double, and there are three forms of long double. The 80-bit format used 2538 128-bit format used by PowerPC (two adjacent doubles) is represented by 2539 ``0xM`` followed by 32 hexadecimal digits. The IEEE 128-bit format is [all …]
|
| /external/llvm/docs/CommandGuide/ |
| D | llvm-cov.rst | 14 work with ``gcov``\-style coverage or with ``clang``\'s instrumentation 180 ``clang`` use the ``-fprofile-instr-generate`` and ``-fcoverage-mapping`` 181 flags. If linking with the ``clang`` driver, pass ``-fprofile-instr-generate`` 188 typically called ``default.profraw``, which can be converted to a format that 212 Show the execution counts for each region by displaying a caret that points to 213 the character where the region starts. 217 Show the execution counts for each line if there is only one region on the 249 .. option:: -region-coverage-gt=<N> 251 Show code coverage only for functions with region coverage greater than the 254 .. option:: -region-coverage-lt=<N> [all …]
|
| /external/clang/include/clang/Basic/ |
| D | AttrDocs.td | 13 NOTE: This file is automatically generated by running clang-tblgen 124 …let Heading = "assert_capability (assert_shared_capability, clang::assert_capability, clang::asser… 133 …let Heading = "acquire_capability (acquire_shared_capability, clang::acquire_capability, clang::ac… 141 …= "try_acquire_capability (try_acquire_shared_capability, clang::try_acquire_capability, clang::tr… 152 …let Heading = "release_capability (release_shared_capability, clang::release_capability, clang::re… 186 a future version of clang. Also, the ABI is not standardized and the name 276 instruct clang to call ``__builtin_object_size(param, Type)`` at each callsite 489 // void nodupfunc() [[clang::noduplicate]]; 729 The ``clang::fallthrough`` attribute is used along with the 752 [[clang::fallthrough]]; [all …]
|
| D | DiagnosticSemaKinds.td | 2169 "strftime format attribute requires 3rd parameter to be 0">; 2171 "format attribute requires variadic function">; 2172 def err_format_attribute_not : Error<"format argument not %0">; 2175 "format attribute cannot specify the implicit this argument as the format " 5390 "format string is not a string literal (potentially insecure)">, 5393 "format string is not a string literal">, 6408 "%select{function|block|method|constructor}2; expected type from format " 6413 "%select{function|block|method|constructor}2; expected type from format " 6437 "%select{function|block|method|constructor}2; expected type from format " 6601 "accepted due to -fheinous-gnu-extensions, but clang may remove support " [all …]
|
| /external/clang/test/ARCMT/ |
| D | objcmt-arc-cf-annotations.m.result | 8 #define CF_IMPLICIT_BRIDGING_ENABLED _Pragma("clang arc_cf_code_audited begin") 16 #define CF_IMPLICIT_BRIDGING_DISABLED _Pragma("clang arc_cf_code_audited end") 138 extern void NSLog(NSString *format, ...) __attribute__((format(__NSString__, 1, 2))); 296 - (CGImageRef)createCGImage:(CIImage *)im fromRect:(CGRect)r format:(CIFormat)f colorSpace:(CGC… 409 // Test case 'f4' differs for region store and basic store. See 410 // retain-release-region-store.m and retain-release-basic-store.m. 793 // <rdar://problem/6257780> clang checker fails to catch use-after-release 983 // <rdar://problem/6902710> clang: false positives w/QC and CoreImage methods 992 [context createCGImage:img fromRect:rect format:form colorSpace:cs]; // expected-warning{{leak}} 997 // misinterpreted by clang scan-build [all …]
|
| D | objcmt-arc-cf-annotations.m | 8 #define CF_IMPLICIT_BRIDGING_ENABLED _Pragma("clang arc_cf_code_audited begin") 16 #define CF_IMPLICIT_BRIDGING_DISABLED _Pragma("clang arc_cf_code_audited end") 132 extern void NSLog(NSString *format, ...) __attribute__((format(__NSString__, 1, 2))); 278 - (CGImageRef)createCGImage:(CIImage *)im fromRect:(CGRect)r format:(CIFormat)f colorSpace:(CGC… 379 // Test case 'f4' differs for region store and basic store. See 380 // retain-release-region-store.m and retain-release-basic-store.m. 751 // <rdar://problem/6257780> clang checker fails to catch use-after-release 941 // <rdar://problem/6902710> clang: false positives w/QC and CoreImage methods 950 [context createCGImage:img fromRect:rect format:form colorSpace:cs]; // expected-warning{{leak}} 955 // misinterpreted by clang scan-build [all …]
|
| /external/valgrind/ |
| D | NEWS | 117 in the region of 0% to 7% for those targets only. 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 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 1138 315345 cl-format.xml and callgrind/dump.c don't agree on using cfl= or cfi= 1289 n-i-bz OSX build w/ clang: asserts at startup [all …]
|
| /external/e2fsprogs/ |
| D | RELEASE-NOTES | 43 the changes to enable the qcow2 format broke this e2image mode. 117 Fix sparse, gcc -Wall and clang nits. 265 Fix gcc -Wall and clang nits. 280 * add -e option to print extent format, even when FIBMAP is used 281 * add -X option to print extents in hexadecimal format 481 Add support for e2fsprogs to be compiled using clang/LLVM. 709 jbd2 format, as well as f_eofblocks which tests the new handling of 1044 The e2image program now supports the qcow2 format, which is a more 1139 data blocks of a particular inode in a format which is useful for 1336 Debugfs now uses a more concicse format for listing extents in its [all …]
|
| /external/icu/icu4j/main/shared/data/ |
| D | Transliterator_Han_Latin_Definition.txt | 12 邊幣 < border\-region\-currency\-\(consisting\-of\-the\-currency\-notes\-issued\-by\-the\-border\-reg… 144 阿不來提\.阿不都熱西提 < abdulaidi\-amudurexiti\-\(chairman\-of\-xinjiang\-autonomous\-region\); 527 烏魯木齊 < urumqi\-\(capital\-of\-xinjiang\-autonomous\-region\); 1228 首府 < capital\-city\-of\-an\-autonomous\-region; 1355 肓 < region\-between\-heart\-and\-diaphragm; 1463 新疆 < xinjiang\-\(uygur\-autonomous\-region\); 1784 特區 < special\-\(administrative\)\-region; 2204 特別行政區 < special\-administrative\-region; 2481 自治區 < autonomous\-region\-\(in\-china\); 5042 亞洲與太平洋地區 < asia\-pacific\-region; [all …]
|
| /external/clang/test/Analysis/ |
| D | retain-release.m | 2 …tainRelease,osx.cocoa.ClassRelease,osx.cocoa.RetainCount -analyzer-store=region -fblocks -verify -… 3 …tainRelease,osx.cocoa.ClassRelease,osx.cocoa.RetainCount -analyzer-store=region -fblocks -verify -… 120 extern void NSLog(NSString *format, ...) __attribute__((format(__NSString__, 1, 2))); 273 - (CGImageRef)createCGImage:(CIImage *)im fromRect:(CGRect)r format:(CIFormat)f colorSpace:(CGC… 374 // Test case 'f4' differs for region store and basic store. See 375 // retain-release-region-store.m and retain-release-basic-store.m. 746 // <rdar://problem/6257780> clang checker fails to catch use-after-release 936 // <rdar://problem/6902710> clang: false positives w/QC and CoreImage methods 945 [context createCGImage:img fromRect:rect format:form colorSpace:cs]; // expected-warning{{leak}} 950 // misinterpreted by clang scan-build [all …]
|