| /external/swiftshader/third_party/LLVM/docs/HistoricalNotes/ |
| D | 2001-06-20-.NET-Differences.txt | 6 One significant difference between .NET CLR and our VM is that the CLR
13 This is an important difference because I think there are some significant
14 advantages to have a much lower level VM layer, and do significant static
|
| /external/llvm/docs/HistoricalNotes/ |
| D | 2001-06-20-.NET-Differences.txt | 6 One significant difference between .NET CLR and our VM is that the CLR
13 This is an important difference because I think there are some significant
14 advantages to have a much lower level VM layer, and do significant static
|
| /external/swiftshader/third_party/llvm-7.0/llvm/docs/HistoricalNotes/ |
| D | 2001-06-20-.NET-Differences.txt | 6 One significant difference between .NET CLR and our VM is that the CLR
13 This is an important difference because I think there are some significant
14 advantages to have a much lower level VM layer, and do significant static
|
| /external/v8/tools/ |
| D | perf-compare.py | 75 def __init__(self, significant, notable, percentage_string): argument
76 self.significant_ = significant
105 significant = False
119 significant = True
124 return ResultsDiff(significant, notable, percentage_string)
|
| /external/python/dateutil/changelog.d/ |
| D | template.rst | 22 No significant changes.
29 No significant changes.
|
| /external/mesa3d/docs/specs/ |
| D | EGL_MESA_drm_image_formats.txt | 70 endian, 32-bit quantity, with alpha in the most significant 2 bits,
74 16-bit quantity, with alpha in the most significant bit, followed by
78 16-bit quantity, with red in the 5 most significant bits, followed by
|
| D | MESA_shader_integer_functions.txt | 48 added functionality requires significant hardware support. There are many
77 position of the most or least significant set bit, count the number
291 the parameter <exp>. For a floating-point value of zero, the significant
339 least significant bits of corresponding component of the result. For
340 unsigned data types, the most significant bits of the result will be set
341 to zero. For signed data types, the most significant bits will be set to
348 The function bitfieldInsert() inserts the <bits> least significant bits of
367 The function findLSB() returns the bit number of the least significant one
371 The function findMSB() returns the bit number of the most significant bit
373 result will be the bit number of the most significant one bit. For
[all …]
|
| /external/llvm/lib/Target/Lanai/ |
| D | LanaiInstrFormats.td | 68 // is set to the most significant bit of the result.
72 // set if the sign (most significant) bits of the input operands are
78 // a carry generated out of the most significant when performing the
81 // significant bit discarded by the shift operation. For all other
251 // All part-word loads write the least significant part of the
253 // All part-word stores store the least significant part-word of the
480 // Memory(ea) <- (least significant byte of Rr)
482 // Memory(ea) <- (least significant half-word of Rr)
495 // All part-word loads write the part-word into the least significant
497 // sign-extended. All part-word stores store the least significant
|
| /external/swiftshader/third_party/llvm-7.0/llvm/lib/Target/Lanai/ |
| D | LanaiInstrFormats.td | 68 // is set to the most significant bit of the result.
72 // set if the sign (most significant) bits of the input operands are
78 // a carry generated out of the most significant when performing the
81 // significant bit discarded by the shift operation. For all other
251 // All part-word loads write the least significant part of the
253 // All part-word stores store the least significant part-word of the
480 // Memory(ea) <- (least significant byte of Rr)
482 // Memory(ea) <- (least significant half-word of Rr)
495 // All part-word loads write the part-word into the least significant
497 // sign-extended. All part-word stores store the least significant
|
| /external/zlib/src/doc/ |
| D | rfc1951.txt | 250 significant bit, and since we write numbers with the most-
251 significant digit on the left, we also write bytes with the most-
252 significant bit on the left. In the diagrams below, we number the
253 bits of a byte so that bit 0 is the least-significant bit, i.e.,
262 the least-significant byte first (at the lower memory address).
271 | + more significant byte = 2 x 256
272 + less significant byte = 8
295 with the least-significant bit of the byte.
297 starting with the least-significant bit of the data
300 significant bit of the code.
[all …]
|
| D | rfc1950.txt | 186 significant bit, and since we write numbers with the most-
187 significant digit on the left, we also write bytes with the most-
188 significant bit on the left. In the diagrams below, we number the
189 bits of a byte so that bit 0 is the least-significant bit, i.e.,
198 the MOST-significant byte first (at the lower memory address).
207 | + less significant byte = 8
208 + more significant byte = 2 x 256
329 significant-byte first (network) order.
|
| D | rfc1952.txt | 196 significant bit, and since we write numbers with the most-
197 significant digit on the left, we also write bytes with the most-
198 significant bit on the left. In the diagrams below, we number the
199 bits of a byte so that bit 0 is the least-significant bit, i.e.,
212 the least-significant byte first (at the lower memory address).
221 | + more significant byte = 2 x 256
222 + less significant byte = 8
327 of the two least significant bytes of the CRC32 for all
|
| /external/python/cpython2/Lib/test/ |
| D | formatfloat_testcases.txt | 234 -- it mean to have no significant digits?); in practice, it's interpreted
299 -- exactly <precision> significant digits.
355 -- str truncates to 12 significant digits
|
| /external/llvm/lib/Fuzzer/test/ |
| D | fuzzer-trace-pc.test | 4 // FIXME: The test below uses a significant amount of memory on OSX and
|
| /external/python/cpython3/Doc/tutorial/ |
| D | floatingpoint.rst | 57 the numerator using the first 53 bits starting with the most significant bit and
89 the one with 17 significant digits, ``0.10000000000000001``. Starting with
99 …t output, you may wish to use string formatting to produce a limited number of significant digits::
101 >>> format(math.pi, '.12g') # give 12 significant digits
279 older versions of Python), round the result to 17 significant digits::
|
| /external/brotli/ |
| D | .editorconfig | 32 # - trailing whitespace is significant
|
| /external/swiftshader/third_party/llvm-7.0/llvm/docs/ |
| D | Extensions.rst | 253 ``.linker-options`` though the name is not significant as it is identified by
335 This section is used to mark symbols as address-significant, i.e. the address
340 Any sections referred to by symbols that are not marked as address-significant
345 referring to the symbol table indexes of the address-significant symbols.
354 this directive, all symbols are considered address-significant.
360 This marks ``sym`` as address-significant.
|
| /external/swiftshader/third_party/llvm-7.0/llvm/lib/Target/RISCV/ |
| D | RISCVInstrInfoC.td | 93 // A 7-bit unsigned immediate where the least significant two bits are zero.
107 // A 8-bit unsigned immediate where the least significant two bits are zero.
121 // A 8-bit unsigned immediate where the least significant three bits are zero.
135 // A 9-bit signed immediate where the least significant bit is zero.
149 // A 9-bit unsigned immediate where the least significant three bits are zero.
163 // A 10-bit unsigned immediate where the least significant two bits are zero
179 // A 10-bit signed immediate where the least significant four bits are zero.
194 // A 12-bit signed immediate where the least significant bit is zero.
|
| /external/grpc-grpc/tools/profiling/microbenchmarks/bm_diff/ |
| D | README.md | 17 made some significant changes and want to see some data. From your branch, run
24 Lastly it will compute the statistically significant performance differences
78 between them, and prints any significant improvements or regressions. It takes
|
| /external/icu/icu4j/perf-tests/data/conversion/ |
| D | english.txt | 13 …ndard, and the availability of tools supporting it, are among the most significant recent global s…
15 …de into client-server or multi-tiered applications and websites offers significant cost savings ov…
|
| /external/llvm/test/CodeGen/X86/ |
| D | fast-isel-select.ll | 2 ; Make sure we only use the less significant bit of the value that feeds the
|
| /external/markdown/docs/ |
| D | release-2.0.txt | 5 making. We have rewritten significant portions of the code, dramatically
24 summary of the significant changes:
|
| /external/python/cpython3/Doc/c-api/ |
| D | marshal.rst | 14 Numeric values are stored with the least significant byte first.
25 the least-significant 32 bits of *value*; regardless of the size of the
|
| /external/neon_2_sse/ |
| D | ReadMe.md | 9 For significant performance improvement in some cases you might need to define USE_SSE4 in your pro…
|
| /external/swiftshader/third_party/llvm-7.0/llvm/test/CodeGen/X86/ |
| D | fast-isel-select.ll | 4 ; Make sure we only use the less significant bit of the value that feeds the
|