Searched refs:represent (Results 1 – 25 of 1537) sorted by relevance
12345678910>>...62
/external/snakeyaml/src/test/java/org/yaml/snakeyaml/issues/issue132/ |
D | ScalarEventTagTest.java | 47 Node intNode = yaml.represent(7); in testDump() 55 Node strNode = yaml.represent("7"); in testDump()
|
/external/tensorflow/ |
D | METADATA | 4 "using data flow graphs. The graph nodes represent mathematical operations, " 5 "while the graph edges represent the multidimensional data arrays (tensors) "
|
/external/llvm/test/MC/ARM/ |
D | error-location.s | 13 @ CHECK: :[[@LINE+1]]:{{[0-9]+}}: error: No relocation available to represent this relative express… 16 @ CHECK: :[[@LINE+1]]:{{[0-9]+}}: error: Cannot represent a difference across sections
|
/external/llvm/include/llvm/Target/ |
D | TargetItinerary.td | 19 // Processor functional unit - These values represent the function units 43 // Instruction stage - These values represent a non-pipelined step in 45 // discrete time slots needed to complete the stage. Units represent 73 // Instruction itinerary classes - These values represent 'named' instruction 121 // Processor itineraries - These values represent the set of all itinerary
|
/external/llvm-project/libcxx/docs/DesignDocs/ |
D | FileTimeType.rst | 35 To represent the range and resolution of ``timespec``, we need to (A) have 74 ``std::system_clock`` does. As a result, it can represent time points about 78 ``timespec`` can represent time points +/- 292 billion years from the epoch 95 point that it can't represent. This can cause the call to ``last_write_time`` 153 that is able to represent a larger range than ``timespec``. At least in 159 create a time point beyond what the filesystem can represent. Two particular 175 now we can represent any time point the filesystem can, so users won't be forced 195 just the values they can represent. We need to consider the effects they will 251 to represent the ``file_time_type``. It only seems natural seeing as that's 280 tick period it is being used to represent, but ``timespec`` is setup to assume [all …]
|
/external/libcxx/docs/DesignDocs/ |
D | FileTimeType.rst | 35 To represent the range and resolution of ``timespec``, we need to (A) have 74 ``std::system_clock`` does. As a result, it can represent time points about 78 ``timespec`` can represent time points +/- 292 billion years from the epoch 95 point that it can't represent. This can cause the call to ``last_write_time`` 152 that is able to represent a larger range than ``timespec``. At least in 158 create a time point beyond what the filesystem can represent. Two particular 174 now we can represent any time point the filesystem can, so users won't be forced 194 just the values they can represent. We need to consider the effects they will 250 to represent the ``file_time_type``. It only seems natural seeing as that's 279 tick period it is being used to represent, but ``timespec`` is setup to assume [all …]
|
/external/tensorflow/tensorflow/core/protobuf/ |
D | struct.proto | 18 // loading the SavedModel, we need to represent "True" and "False". 23 // after load to the right saved TensorFlow function, we need to represent the 109 // A protobuf to represent tf.TensorSpec. 116 // A protobuf to represent tf.BoundedTensorSpec.
|
/external/llvm-project/clang/include/clang/Basic/ |
D | TypeNodes.td | 8 /// A type node that is only used to represent dependent types in C++. For 9 /// example, DependentTemplateSpecializationType is used to represent types 14 /// A type node that is never used to represent a canonical type, which is to 27 /// represent the alignment attribute on typedefs, and so it is necessary to
|
/external/llvm/include/llvm/CodeGen/ |
D | ValueTypes.td | 106 // Pseudo valuetype to represent "vector of any size" 109 // Pseudo valuetype to represent "float of any format" 112 // Pseudo valuetype to represent "integer of any bit width" 118 // Pseudo valuetype to represent "any type of any size".
|
/external/llvm-project/llvm/include/llvm/Target/ |
D | TargetItinerary.td | 18 // Processor functional unit - These values represent the function units 42 // Instruction stage - These values represent a non-pipelined step in 44 // discrete time slots needed to complete the stage. Units represent 72 // Instruction itinerary classes - These values represent 'named' instruction 120 // Processor itineraries - These values represent the set of all itinerary
|
/external/swiftshader/third_party/llvm-10.0/llvm/include/llvm/Target/ |
D | TargetItinerary.td | 18 // Processor functional unit - These values represent the function units 42 // Instruction stage - These values represent a non-pipelined step in 44 // discrete time slots needed to complete the stage. Units represent 72 // Instruction itinerary classes - These values represent 'named' instruction 120 // Processor itineraries - These values represent the set of all itinerary
|
/external/llvm-project/mlir/include/mlir/Dialect/Quant/ |
D | QuantOpsBase.td | 37 // A primitive type that can represent a real value. This is either a 43 // A primitive type that can represent a storage value. This is either an
|
/external/llvm-project/llvm/docs/DependenceGraphs/ |
D | index.rst | 31 into special nodes called pi-blocks. pi-blocks represent cycles of data 132 …represent three main program components, namely *assignment statements*, *for loop headers* and *w… 133 … represent the *flow-*, *anti-*, *output-*, and *input-* dependencies. However, *loop dependencies…
|
/external/llvm-project/clang-tools-extra/docs/clang-tidy/checks/ |
D | bugprone-too-small-loop-variable.rst | 7 which means this type can't represent all values which are part of the 17 This ``for`` loop is an infinite loop because the ``short`` type can't represent
|
/external/llvm-project/llvm/test/CodeGen/AArch64/GlobalISel/ |
D | postlegalizer-lowering-adjust-icmp-imm.mir | 18 ; log_2(4096) == 12, so we can represent this as a 12 bit value with a 52 ; log_2(4096) == 12, so we can represent this as a 12 bit value with a 86 ; log_2(4096) == 12, so we can represent this as a 12 bit value with a 120 ; log_2(4096) == 12, so we can represent this as a 12 bit value with a 154 ; log_2(4096) == 12, so we can represent this as a 12 bit value with a 188 ; log_2(4096) == 12, so we can represent this as a 12 bit value with a 222 ; log_2(4096) == 12, so we can represent this as a 12 bit value with a 256 ; log_2(4096) == 12, so we can represent this as a 12 bit value with a 290 ; log_2(8192) == 13, so we can represent this as a 12 bit value with a 326 ; log_2(8192) == 13, so we can represent this as a 12 bit value with a [all …]
|
/external/flatbuffers/reflection/ |
D | reflection.fbs | 1 // This schema defines objects that represent a parsed schema, like 4 // It can even ... represent itself (!)
|
/external/snakeyaml/src/test/java/examples/jodatime/ |
D | JodaTimeFlowStylesTest.java | 51 Node node1 = dumper.represent(bean); in testLoadBeanWithBlockFlow() 55 Node node2 = dumper2.represent(bean); in testLoadBeanWithBlockFlow()
|
/external/libabigail/src/ |
D | abg-reporter-priv.h | 132 represent(const diff_context& ctxt, 153 represent(const var_diff_sptr &diff,
|
/external/python/cpython3/Doc/c-api/ |
D | contextvars.rst | 33 The C structure used to represent a :class:`contextvars.Context` 38 The C structure used to represent a :class:`contextvars.ContextVar` 43 The C structure used to represent a :class:`contextvars.Token` object.
|
/external/python/cpython2/Doc/library/ |
D | aetypes.rst | 12 The :mod:`aetypes` defines classes used to represent Apple Event data 40 The :mod:`AEObjects` module defines the following classes to represent Apple 132 represent AppleScript classes and properties in Python:
|
/external/googletest/googletest/scripts/ |
D | README.md | 4 represent mosty historical artifacts and supported by the community only. There
|
/external/googletest/googlemock/scripts/ |
D | README.md | 4 represent mostly historical artifacts and supported by the community only. There
|
/external/tensorflow/tensorflow/core/api_def/base_api/ |
D | api_def_BroadcastArgs.pbtxt | 8 Given `s0` and `s1`, tensors that represent shapes, compute `r0`, the
|
D | api_def_DatasetCardinality.pbtxt | 13 The cardinality of `input_dataset`. Named constants are used to represent
|
D | api_def_ExperimentalDatasetCardinality.pbtxt | 13 The cardinality of `input_dataset`. Named constants are used to represent
|
12345678910>>...62