| /system/core/include/cutils/ |
| sockets.h | 141 * on Windows. This can give significant speedup compared to calling send()
|
| /system/core/libmemunreachable/ |
| README.md | 8 In the default (zero-overhead) mode, the returned data on leaks is limited to the address, approximate (upper bound) size, and the the first 32 bytes of the contents of the leaked allocation. If malloc_debug backtraces are enabled they will be included in the leak information, but backtracing allocations requires significant overhead.
|
| /system/update_engine/update_manager/ |
| chromeos_policy.h | 38 // Significant iff |do_increment_failures| is false and |backoff_expiry| is
|
| /toolchain/binutils/binutils-2.25/gas/ |
| CONTRIBUTORS | 108 you've contributed significant work and are not mentioned on this list, and
|
| /toolchain/binutils/binutils-2.25/gas/config/ |
| atof-ieee.c | 411 Bits n-1:0 (if any) are most significant bits of fraction.
412 Bits 15:0 of the next word(s) are the next most significant bits.
422 /* Seek (and forget) 1st significant bit. */
711 should be emitted most significant littlenum first.
|
| tc-tic6x.h | 92 least-significant byte of the last instruction in it (for setting
|
| /toolchain/binutils/binutils-2.25/include/ |
| floatformat.h | 28 fields is contiguous. We number the bits with 0 being the most significant
|
| /toolchain/binutils/binutils-2.25/include/opcode/ |
| tic54x.h | 91 /* The significant bits in the opcode. Other bits are zero.
|
| /toolchain/binutils/binutils-2.25/ld/emultempl/ |
| cr16elf.em | 70 a significant amount of time and memory. */
|
| /toolchain/binutils/binutils-2.25/libiberty/ |
| floatformat.c | 436 /* Start at the least significant part of the field. */
575 /* Start at the least significant part of the field. */
689 /* The bits we want are in the most significant MANT_BITS bits of
690 mant_long. Move them to the least significant. */
|
| /external/icu/icu4c/source/i18n/ |
| decNumberLocal.h | 280 uByte *msd; /* -> most significant digit */
345 /* In DFISZERO the first test checks the least-significant word */
397 /* [the top 2 bits will always be in the more-significant uInt] */
451 /* In-line sequence to convert least significant 10 bits of uInt */
540 /* a base-billion uInt array, with the least-significant */
594 /* the MSD), with the least-significant 0-999 'digit' at offset 0.*/
[all...] |
| /frameworks/av/media/libstagefright/codecs/amrnb/enc/src/ |
| amrencode.cpp | 539 least significant bit) to WMF (aka, non-IF2). The WMF format stores the data
540 in octets. The least significant 4 bits of the first octet contains the 3GPP
541 frame type information and the most significant 4 bits are zeroed out. The
548 The least significant nibble of the first octet contains the 3GPP frame type
549 and the most significant nibble contains the first 4 encoded speech bits. The
567 pEncOutput in the little endian configuration, i.e., least significant byte,
568 followed by most significant byte. The num_enc_bytes is set to
|
| /frameworks/opt/telephony/src/java/com/google/android/mms/pdu/ |
| PduComposer.java | 210 * ; with the most significant bit set to one (1xxx xxxx) and with
211 * ; the value in the remaining least significant bits.
254 * ; most significant octet encoded first (big-endian representation).
359 * and place them in the payloads of multiple octets. The most significant
360 * bits are placed in the first octets with the least significant bits
[all...] |
| /packages/apps/Messaging/src/com/android/messaging/mmslib/pdu/ |
| PduComposer.java | 217 * ; with the most significant bit set to one (1xxx xxxx) and with
218 * ; the value in the remaining least significant bits.
261 * ; most significant octet encoded first (big-endian representation).
366 * and place them in the payloads of multiple octets. The most significant
367 * bits are placed in the first octets with the least significant bits
[all...] |
| /prebuilts/gcc/linux-x86/host/x86_64-w64-mingw32-4.8/share/info/ |
| gmp.info-2 | 47 * Call HGCD recursively, on the most significant N/2 limbs. Apply the
55 * Call HGCD recursively, on the most significant N/2 limbs of the
67 subquadratic GCD chops off the most significant third of the limbs (the
94 code chops off the most significant half of the inputs for the call to
95 HGCD in the first iteration, and the most significant two thirds for
256 A significant fraction of non-squares can be quickly identified by
367 Since the base case produces digits from least to most significant
656 significant when N is small, and when N is large clearly the multiply
673 The assembly subroutines in GMP are the most significant source of
730 `mpn_mul_basecase' and `mpn_sqr_basecase' give significant speedups
[all...] |
| /docs/source.android.com/src/devices/sensors/ |
| sensor-types.jd | 259 <a href="#significant_motion">Significant motion</a>, which are usually based on
358 <td><p><a href="#significant_motion">Significant motion</a> <img
415 <h3 id="significant_motion">Significant motion</h3>
421 <p>A significant motion detector triggers when the detecting a ?significant
423 <p>Examples of such significant motions are:</p>
428 <p>Examples of situations that do not trigger significant motion:</p>
434 <p>At the high level, the significant motion detector is used to reduce the power
437 on significant motion to wake the device up when the user is changing location.</p>
[all...] |
| batching.jd | 30 <p>Batching can enable significant power savings by preventing the SoC from waking
169 counter-productive. The goal here is to save significant amounts of power.
|
| /external/deqp/modules/gles3/performance/ |
| es3pDepthTests.cpp | [all...] |
| /external/llvm/lib/Support/ |
| APInt.cpp | [all...] |
| APFloat.cpp | 341 significant BITS bits. */
410 when the least significant BITS are truncated. BITS cannot be
526 significant nibble. Write out exactly COUNT hexdigits, return
976 // Note that there are three significant bits at the left-hand side of the
1034 // Convert the result having "2 * precision" significant-bits back to the one
1035 // having "precision" significant-bits. First, move the radix point from
1042 // the radix point (i.e. "MSB . rest-significant-bits").
[all...] |
| /external/valgrind/ |
| NEWS.old | 66 3.3.0 is a feature release with many significant improvements and the
82 has some significant improvements aimed at reducing the false error
474 3.2.0 is a feature release with many significant improvements and the
710 3.1.0 is a feature release with a number of significant improvements:
[all...] |
| /art/runtime/base/ |
| bit_utils.h | 65 // Find the bit position of the most significant bit (0-based), or -1 if there were no bits set.
74 // Find the bit position of the least significant bit (0-based), or -1 if there were no bits set.
|
| /art/runtime/ |
| utils.h | 82 // True, if the most significant bits of divisor are 0.
88 // True, if the most significant bits of divisor are 0.
|
| /cts/hostsidetests/sustainedperf/dhrystone/ |
| dhry.h | 69 * had small (though not significant) differences.
73 * removing significant statements.
|
| /docs/source.android.com/src/devices/tech/power/ |
| mgmt.jd | 135 <a href="{@docRoot}devices/sensors/sensor-types.html#significant_motion">Significant
160 <li>Device is stationary (using significant motion detector).</li>
|
