clang\-format\-region (reference) in projects: external

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

Searched +refs:clang +refs:format +refs:region (Results 1 – 25 of 32) 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	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 124 region counts (even in macro expansions): 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`
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
/external/swiftshader/third_party/llvm-7.0/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 describe 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 872 …but not in LLVM unwinder (`libunwind <https://clang.llvm.org/docs/Toolchain.html#unwind-library>`_… [all …]
D	AMDGPUUsage.rst	23 Use the ``clang -target <Architecture>-<Vendor>-<OS>-<Environment>`` option to 75 Use the ``clang -mcpu <Processor>`` option to specify the AMD GPU processor. The 231 Use the ``clang -m[no-]<TargetFeature>`` option to specify the AMD GPU 270 The memory space names used in the table, aside from the region memory space, is 889 runtime) may be embedded into the DWARF v5 line table using the ``clang 1053 The format string passed to the 1450 for a memory region with the kernarg property for the kernel agent that will 2551 The memory model does not support the region address space which is treated as 3976 The following table illustrates the required format: 4623 .. [CLANG-ATTR] `Attributes in Clang <http://clang.llvm.org/docs/AttributeReference.html>`__
D	LangRef.rst	457 On targets that use the ELF object file format, default visibility 621 region of memory, and all memory objects in LLVM are accessed through 1248 have a particular format. Specifically, it must begin with a sequence of 1254 makes the format of the prologue data highly target dependent. 1519 This attribute indicates that the function will trigger a guard region 1521 no further apart than the size of the guard region to a previous 1572 It defines the size of the guard region. It ensures that if the function 1573 may use more stack space than the size of the guard region, stack probing 1616 `SafeStack <http://clang.llvm.org/docs/SafeStack.html>`_ 2455 source through the clang front end, for example. It is then preserved through [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 239 .. option:: -format=<FORMAT> 241 Use the specified output format. The supported formats are: "text", "html". 261 .. option:: -region-coverage-gt=<N> [all …]
/external/swiftshader/third_party/llvm-7.0/llvm/docs/CommandGuide/
D	llvm-cov.rst	14 work with ``gcov``\-style coverage or with ``clang``\'s instrumentation 181 ``clang`` use the ``-fprofile-instr-generate`` and ``-fcoverage-mapping`` 182 flags. If linking with the ``clang`` driver, pass ``-fprofile-instr-generate`` 189 typically called ``default.profraw``, which can be converted to a format that 214 Show the execution counts for each region by displaying a caret that points to 215 the character where the region starts. Defaults to false. 219 Show the execution counts for each line if there is only one region on the 253 .. option:: -format=<FORMAT> 255 Use the specified output format. The supported formats are: "text", "html". 260 only supported for the html format. [all …]
D	llvm-mca.rst	30 ``LLVM-MCA-BEGIN`` marks the beginning of a code region. A comment starting with 31 substring ``LLVM-MCA-END`` marks the end of a code region. For example: 40 region can have an optional description. If no user-defined region is specified, 41 then :program:`llvm-mca` assumes a default region which contains every 42 instruction in the input file. Every region is analyzed in isolation, and the 44 code region. 59 So for example, you can compile code with clang, output assembly, and pipe it 64 $ clang foo.c -O2 -target x86_64-unknown-unknown -S -o - \| llvm-mca -mcpu=btver2 70 …$ clang foo.c -O2 -target x86_64-unknown-unknown -mllvm -x86-asm-syntax=intel -S -o - \| llvm-mca -… 105 the AT&T (vic. Intel) assembly format for the code printed out by the tool in
/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 289 on when overloads are resolved. In the example below, clang will emit a 325 instruct clang to call ``__builtin_object_size(param, Type)`` at each callsite 547 // void nodupfunc() [[clang::noduplicate]]; 832 let Heading = "nodiscard, warn_unused_result, clang::warn_unused_result, gnu::warn_unused_result"; [all …]
D	DiagnosticSemaKinds.td	2225 "strftime format attribute requires 3rd parameter to be 0">; 2227 "format attribute requires variadic function">; 2228 def err_format_attribute_not : Error<"format argument not %0">; 2231 "format attribute cannot specify the implicit this argument as the format " 5558 "format string is not a string literal (potentially insecure)">, 5561 "format string is not a string literal">, 6622 "%select{function\|block\|method\|constructor}2; expected type from format " 6627 "%select{function\|block\|method\|constructor}2; expected type from format " 6651 "%select{function\|block\|method\|constructor}2; expected type from format " 6826 "accepted due to -fheinous-gnu-extensions, but clang may remove support " [all …]
/external/yapf/
D	README.rst	26 YAPF takes a different approach. It's based off of 'clang-format', developed by 85 runs under. Therefore, if you format Python 3 code with YAPF, run YAPF itself 200 a = 'hello {}'.format('world') 217 a = 'hello {}'.format('world') 255 that we want to format. The lines are 1-based indexed. It can be used by 599 with development. It will format things to coincide with the style guide, but 636 We wanted to use clang-format's reformatting algorithm. It's very powerful and 639 to convert to using clang-format's algorithm. 705 decision (left hand branch) within the unbreakable region.
/external/icu/icu4c/source/test/depstest/
D	dependencies.txt	`42 # UBSan=UndefinedBehaviorSanitizer, clang -fsanitize=bounds 827 region localedata genderinfo charset_detector spoof_detection 836 group: region 837 region.o uregion.o 908 resourcebundle simpleformatter format uclean_i18n 942 decnumber double_conversion formattable format units 986 decnumber formattable format units numberformatter numberparser 1022 group: format 1023 format.o fphdlimp.o fpositer.o ufieldpositer.o`
/external/swiftshader/third_party/llvm-7.0/llvm/docs/Proposals/
D	GitHubMove.rst	89 distribute the contents of the repositories depending on region and load. 130 We can thus use this revision number to ensure that e.g. `clang -v` reports a 156 email format unchanged besides the commit URL. 224 A key need is to be able to check out multiple projects (i.e. lldb+clang+llvm or 225 clang+llvm+libcxx for example) at a specific revision. 229 For example, a given version of clang would be 230 <LLVM-12345, clang-5432, libcxx-123, etc.>. 305 * Refactoring across projects is not friendly: taking some functions from clang 368 # Configure LLVM and clang 369 cmake path/to/monorepo -DLLVM_ENABLE_PROJECTS=clang [all …]
/external/clang/test/ARCMT/
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 …]
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 …]
/external/tensorflow/tensorflow/stream_executor/cuda/
D	cuda_dnn.cc	51 #pragma clang diagnostic push 55 #pragma clang diagnostic warning "-Wmismatched-tags" 552 cudnnTensorFormat_t format; in CudnnFilterDescriptor() local 555 format = CUDNN_TENSOR_NCHW; in CudnnFilterDescriptor() 558 format = CUDNN_TENSOR_NHWC; in CudnnFilterDescriptor() 561 format = CUDNN_TENSOR_NCHW_VECT_C; in CudnnFilterDescriptor() 576 CHECK_CUDNN_OK(cudnnSetFilterNdDescriptor(handle_.get(), elem_type, format, in CudnnFilterDescriptor() 1209 for (int region = 0; region < region_count_per_layer; region++) { in Create() local 1217 /w=/nullptr, /linLayerID=/region, in Create() 1224 /w=/nullptr, /linLayerID=/region, in Create() [all …]
/external/libjpeg-turbo/
D	ChangeLog.md	28 chrominance sampling factors), but the JPEG format and the libjpeg API both 212 memory buffer with a specified pixel format and layout. These functions 219 that contains the alpha component index for each pixel format (or -1 if the 220 pixel format lacks an alpha component.) The TurboJPEG Java API now includes a 225 rather than 0. This allows programs to easily determine whether a pixel format 275 3. Fixed a segfault in djpeg that would occur if an output format other than 280 output format other than PPM/PGM, GIF, or Targa is selected along with the 349 (known to occur with GCC 4.x and clang with `-O1` and higher but not with 439 1x2 luminance and 1x1 chrominance sampling factors), but the JPEG format and 499 prevented the code from assembling properly with clang. [all …]
/external/swiftshader/third_party/subzero/docs/
D	DESIGN.rst	136 some of LLVM's bitcode decoding code (for binary-format ``.pexe`` files), again 138 larger due to including code for parsing text-format bitcode files and forming 1254 be selected. Nop instructions are never added inside a bundle_lock region. 1346 <https://developer.chrome.com/native-client/reference/nacl-manifest-format>`_ 1459 <http://clang.llvm.org/docs/AddressSanitizer.html>`_ (ASan) or `ThreadSanitizer 1460 <http://clang.llvm.org/docs/ThreadSanitizer.html>`_ (TSan) support. This is 1465 <http://clang.llvm.org/docs/UsersManual.html#controlling-code-generation>`_ 1467 <http://clang.llvm.org/docs/ControlFlowIntegrity.html>`_ is also under
/external/swiftshader/third_party/subzero/
D	DESIGN.rst	136 some of LLVM's bitcode decoding code (for binary-format ``.pexe`` files), again 138 larger due to including code for parsing text-format bitcode files and forming 1254 be selected. Nop instructions are never added inside a bundle_lock region. 1346 <https://developer.chrome.com/native-client/reference/nacl-manifest-format>`_ 1459 <http://clang.llvm.org/docs/AddressSanitizer.html>`_ (ASan) or `ThreadSanitizer 1460 <http://clang.llvm.org/docs/ThreadSanitizer.html>`_ (TSan) support. This is 1465 <http://clang.llvm.org/docs/UsersManual.html#controlling-code-generation>`_ 1467 <http://clang.llvm.org/docs/ControlFlowIntegrity.html>`_ is also under
/external/freetype/
D	ChangeLog.25	53 (contrary to GNU tar), so force the POSIX-1.1988 format. 127 functions. Since the PCF format doesn't have an official 380 elements, use CSS descendants (of class `section') to format the 1103 Accept overlay format also, but emit warning message in that case. 1914 Fix clang warnings. 1958 * src/sfnt/ttcmap.c (tt_face_build_cmaps): Remove clang warning. 2004 Remove more clang analyzer warnings. 2031 Fix several clang static analyzer dead store warnings. 2228 Fix clang static analyzer and compiler warnings. 2361 Don't check metrics, which this format doesn't have. [all …]
/external/strace/
D	ChangeLog	138 warning reported by clang -Wtautological-constant-out-of-range-compare. 140 build: enable gcc -Woverride-init and clang -Winitializer-overrides. 156 and clang -Winitializer-overrides. 160 macros non-trivially defined for gcc >= 4.2 and clang >= 2.8. 168 tests: workaround clang -Wunneeded-internal-declaration bug. 170 to workaround clang -Wunneeded-internal-declaration bug. 173 to workaround clang -Wunneeded-internal-declaration bug. 1163 (main): Use print_dqfmt to print flags of quota format, improve existing 2222 tests: cast printf arguments to short when %h format qualifier is used. 2223 Reported by clang. [all …]

art
bionic
bootable
build
cts
dalvik
developers
development
device
external
frameworks
hardware
kernel
libcore
libnativehelper
packages
pdk
platform_testing
sdk
system
test
toolchain
tools