Searched
full:large (Results
1501 -
1525 of
7141) sorted by null
<<61626364656667686970>>
/prebuilts/ndk/9/sources/cxx-stl/gnu-libstdc++/4.6/include/tr1/ |
legendre_function.tcc | 200 * but this factor is rather large for large @f$ l @f$ and @f$ m @f$
|
/prebuilts/ndk/9/sources/cxx-stl/gnu-libstdc++/4.7/include/tr1/ |
legendre_function.tcc | 200 * but this factor is rather large for large @f$ l @f$ and @f$ m @f$
|
/prebuilts/ndk/9/sources/cxx-stl/gnu-libstdc++/4.8/include/tr1/ |
legendre_function.tcc | 198 * but this factor is rather large for large @f$ l @f$ and @f$ m @f$
|
/prebuilts/python/darwin-x86/2.7.5/lib/python2.7/test/ |
test_bigmem.py | 11 # - Try not to allocate too many large objects. It's okay to rely on 16 # - Do *not* compare large objects using assertEqual or similar. It's a 21 # - Don't forget to test for large indices, offsets and results and such, 22 # in addition to large sizes. 25 # a large object, make the subobject of a length that is not a power of 31 # testing. Consequently, always make all large allocations based on the 32 # passed-in 'size', and don't rely on the size being very large. Also, 498 # repr() will create a string four times as large as this 'binary [all...] |
test_long_future.py | 33 raise OverflowError("int/int too large to represent as a float") 137 # ... overflow or underflow by large margin
|
test_mutants.py | 149 # test_one was run. So n doesn't have to be large to get an interesting 151 # OTOH, calling with large n is also interesting, to ensure that the fixed
|
/prebuilts/python/linux-x86/2.7.5/lib/python2.7/test/ |
test_bigmem.py | 11 # - Try not to allocate too many large objects. It's okay to rely on 16 # - Do *not* compare large objects using assertEqual or similar. It's a 21 # - Don't forget to test for large indices, offsets and results and such, 22 # in addition to large sizes. 25 # a large object, make the subobject of a length that is not a power of 31 # testing. Consequently, always make all large allocations based on the 32 # passed-in 'size', and don't rely on the size being very large. Also, 498 # repr() will create a string four times as large as this 'binary [all...] |
test_long_future.py | 33 raise OverflowError("int/int too large to represent as a float") 137 # ... overflow or underflow by large margin
|
test_mutants.py | 149 # test_one was run. So n doesn't have to be large to get an interesting 151 # OTOH, calling with large n is also interesting, to ensure that the fixed
|
/sdk/emulator/opengl/host/tools/emugen/ |
ApiGen.cpp | 25 * that instructs the encoder to send large data buffers by a direct 530 // large variables. 537 // Skip over non-large fields 548 // Simple shortcut for the common case where we don't have large variables; 552 // allocate buffer from the stream until the first large variable 581 // encode non-large fields in this fragment 586 // Ensure the fragment is commited if it is followed by a large variable 592 // If we have one or more large variables, write them directly. [all...] |
/tools/external/fat32lib/src/main/java/de/waldheinz/fs/fat/ |
SuperFloppyFormatter.java | 413 "disk too large for FAT16"); 462 IllegalArgumentException("disk too large for FAT12");
|
/frameworks/base/docs/html/training/articles/ |
memory.jd | 135 those pages to the kernel using madvise. So, paired allocations and deallocations of large 324 android.app.ActivityManager#getLargeMemoryClass()} to get an estimate of the large heap size.</p> 326 <p>However, the ability to request a large heap is intended only for a small set of apps that can 327 justify the need to consume more RAM (such as a large photo editing app). <strong>Never request a 328 large heap simply because you've run out of memory</strong> and you need a quick fix—you 330 be retained. Yet, even when you're confident your app can justify the large heap, you should avoid 335 <p>Additionally, the large heap size is not the same on all devices and, when running on 336 devices that have limited RAM, the large heap size may be exactly the same as the regular heap 337 size. So even if you do request the large heap size, you should call {@link 382 surface that look innocuous may in fact have a large amount of overhead. Examples include:</p [all...] |
/external/chromium_org/third_party/icu/source/common/unicode/ |
ustring.h | [all...] |
/external/icu4c/common/unicode/ |
ustring.h | [all...] |
/art/runtime/gc/ |
heap.h | 322 // cleared/extended for large apps. 432 // large object space. 519 // The large object space we are currently allocating into. 618 // Primitive objects larger than this size are put in the large object space.
|
/art/runtime/ |
invoke_arg_array_builder.h | 52 // Analyze shorty to see if we need the large arg array.
|
/bionic/libc/upstream-netbsd/libc/include/isc/ |
dst.h | 115 #define RAW_KEY_SIZE 8192 /*%< large enough to store any key */
|
/bionic/libm/upstream-freebsd/lib/msun/src/ |
e_hypot.c | 38 * large or too tiny
|
k_log.h | 49 * log(1+f) = f - s*(f - R) (if f is not too large)
|
s_ctanh.c | 63 * precision. I also handle large x differently.
|
/bootable/recovery/minzip/ |
SysUtil.c | 28 * Create an anonymous shared memory segment large enough to hold "length"
|
/cts/apps/CtsVerifier/src/com/android/cts/verifier/sensors/ |
MagneticFieldMeasurementTestActivity.java | 116 * the Sensor's sampled data indeed falls into a large StdDev.
|
/cts/tests/tests/database/src/android/database/sqlite/cts/ |
SQLiteProgramTest.java | 105 fail("Should throw exception (index too large)");
|
/cts/tests/tests/hardware/src/android/hardware/cts/ |
SensorMeasurementTests.java | 152 * the Sensor's sampled data indeed falls into a large StdDev.
|
/cts/tests/tests/holo/res/values/ |
strings.xml | 52 <string name="progressbar_large">ProgressBar Large</string>
|
Completed in 3537 milliseconds
<<61626364656667686970>>