| /external/llvm-project/clang/test/Analysis/ |
| D | retain-release-path-notes.m | 110 …aller where a +1 (owning) retain count is expected}} expected-note{{Object with a +0 retain count …
121 …aller where a +1 (owning) retain count is expected}} expected-note{{Object with a +0 retain count …
126 …aller where a +1 (owning) retain count is expected}} expected-note{{Object with a +0 retain count …
131 …aller where a +1 (owning) retain count is expected}} expected-note{{Object with a +0 retain count …
142 …aller where a +1 (owning) retain count is expected}} expected-note{{Object with a +0 retain count …
|
| /external/rust/crates/managed/ |
| D | METADATA | 2 description: "An interface for logically owning objects, whether or not heap allocation is availabl…
|
| D | Cargo.toml.orig | 5 description = "An interface for logically owning objects, whether or not heap allocation is availab…
|
| D | Cargo.toml | 17 description = "An interface for logically owning objects, whether or not heap allocation is availab…
|
| D | README.md | 37 Note that owning a `BorrowMut` in this way does not hide the concrete type inside `BorrowMut`;
|
| /external/rust/cxx/ |
| D | .clang-tidy | 7 -cppcoreguidelines-owning-memory,
|
| /external/tensorflow/tensorflow/stream_executor/tpu/ |
| D | tpu_executable_interface.cc | 119 if (auto owning = device_memory->Release()) { in AllocateOutputMemoryWithInputReuse() local
124 se::DeviceMemoryBase device_memory_base = owning->Release(); in AllocateOutputMemoryWithInputReuse()
|
| /external/autotest/client/site_tests/platform_CryptohomeTPMReOwn/ |
| D | control | 8 CRITERIA = "This will run a test of re-owning the TPM."
|
| /external/boringssl/src/ |
| D | API-CONVENTIONS.md | 216 Likewise, output pointers may be owning or non-owning. Unless otherwise
217 documented, functions output non-owning pointers. The caller is not responsible
225 By convention, functions named `get0` return non-owning pointers. Functions
226 named `new` or `get1` return owning pointers. Functions named `set0` take
|
| /external/tensorflow/tensorflow/compiler/xla/service/cpu/ |
| D | cpu_executable.cc | 272 if (absl::optional<se::OwningDeviceMemory> owning = in CreateResultShapedBuffer() local
278 se::DeviceMemoryBase argument_buffer = owning->Release(); in CreateResultShapedBuffer()
|
| /external/llvm-project/mlir/lib/CAPI/IR/ |
| D | IR.cpp | 146 OwningModuleRef owning = parseSourceString(unwrap(module), unwrap(context)); in mlirModuleCreateParse() local
147 if (!owning) in mlirModuleCreateParse()
149 return MlirModule{owning.release().getOperation()}; in mlirModuleCreateParse()
|
| /external/rust/crates/grpcio-sys/grpc/src/core/ext/filters/client_channel/ |
| D | README.md | 28 a `ConnectedSubchannel` object to the owning channel.
|
| /external/grpc-grpc/src/core/ext/filters/client_channel/ |
| D | README.md | 28 a grpc_subchannel object to the owning channel.
|
| /external/pigweed/pw_span/ |
| D | docs.rst | 8 non-owning view of an array of values. The intent is for this implementation of
|
| /external/llvm-project/clang-tools-extra/docs/clang-tidy/checks/ |
| D | cppcoreguidelines-owning-memory.rst | 1 .. title:: clang-tidy - cppcoreguidelines-owning-memory
3 cppcoreguidelines-owning-memory
|
| /external/llvm-project/lldb/test/Shell/SymbolFile/DWARF/ |
| D | module-ownership.mm | 7 // Verify that the owning module information from DWARF is preserved in the AST.
|
| /external/llvm-project/llvm/test/DebugInfo/Generic/ |
| D | lto-comp-dir.ll | 5 ; unambiguously rely on the comp_dir of their owning CU and use directory '0'
|
| /external/llvm/test/DebugInfo/Generic/ |
| D | lto-comp-dir.ll | 7 ; unambiguously rely on the comp_dir of their owning CU and use directory '0'
|
| /external/skia/experimental/minimal_ios_mtl_skia_app/ |
| D | main.mm | 45 @property (assign, nonatomic) GrDirectContext* grContext; // non-owning pointer.
|
| /external/arm-trusted-firmware/docs/getting_started/ |
| D | rt-svc-writers-guide.rst | 83 each owning entity can place the implementation of its runtime service. The
245 TF-A expects owning entities to follow this recommendation.
288 It is possible that a single owning entity implements multiple sub-services. For
|
| /external/tensorflow/tensorflow/compiler/xla/service/gpu/ |
| D | gpu_executable.cc | 494 absl::optional<tensorflow::se::OwningDeviceMemory> owning = in ExecuteAsyncOnStreamImpl() local
500 se::DeviceMemoryBase argument_buffer = owning->Release(); in ExecuteAsyncOnStreamImpl()
|
| /external/llvm-project/clang/include/clang/Tooling/Syntax/ |
| D | Syntax.td | 12 // - Leaves, owning exactly one token. (syntax::Leaf)
|
| /external/libwebsockets/READMEs/ |
| D | README.lws_dll.md | 126 |remove entry from its owning list|`void lws_dll_remove_track_tail(struct lws_dll *d, struct lws_dl…
|
| /external/llvm-project/mlir/docs/ |
| D | CAPI.md | 104 Numerous MLIR functions return instances of `StringRef` to refer to a non-owning
110 is a non-owning pointer, the caller is in charge of perfoming the copy or
|
| /external/python/cffi/doc/source/ |
| D | using.rst | 52 <cdata 'int *' owning 4 bytes>
54 <cdata 'int[10]' owning 40 bytes>
57 <cdata 'char *' owning 1 bytes>
59 <cdata 'char[]' owning 7 bytes>
223 <cdata 'char[]' owning 6 bytes>
415 # `myfoo`: <cdata 'struct foo_s' owning 8 bytes>
|