HomeSort by relevance Sort by last modified time
    Searched full:efficient (Results 176 - 200 of 2323) sorted by null

1 2 3 4 5 6 78 91011>>

  /frameworks/opt/telephony/
README.txt 5 This makes processing efficient as it minimizes context
  /libcore/luni/src/main/java/java/io/
OutputStream.java 44 * much more efficient than byte-by-byte access.
  /ndk/sources/host-tools/sed-4.2.1/lib/
unlocked-io.h 27 more efficient but not thread-safe. That they're not thread-safe is
  /packages/apps/ContactsCommon/src/com/android/contacts/common/util/
BitmapUtil.java 30 * decode the picture, so it is pretty efficient to run.
  /packages/apps/Email/src/com/android/email/mail/store/imap/
ImapUtility.java 36 * NOTE: Not very efficient - you may wish to preflight this, or perhaps it should check
  /prebuilts/gcc/linux-x86/host/i686-linux-glibc2.7-4.4.3/sysroot/usr/include/rpcsvc/
nlm_prot.x 95 % * The following enums are actually bit encoded for efficient
  /prebuilts/gcc/linux-x86/host/i686-linux-glibc2.7-4.6/sysroot/usr/include/rpcsvc/
nlm_prot.x 95 % * The following enums are actually bit encoded for efficient
  /prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.7-4.6/sysroot/usr/include/rpcsvc/
nlm_prot.x 95 % * The following enums are actually bit encoded for efficient
  /prebuilts/tools/common/proguard/proguard4.7/docs/manual/
wtk.html 30 up to date and it solves some problems. It is also somewhat more efficient,
  /docs/source.android.com/src/devices/tech/test_infra/tradefed/
index.jd 41 usecases where tradefed could enable efficient, scalable test practices.</p>
51 help make each of their test processes efficient, flexible, and scalable.</p>
  /external/chromium/sdch/open-vcdiff/
ChangeLog 56 encoder, but finds better string matches, producing a more efficient
115 the most efficient version of memcmp is used in the encoder's inner loop.
  /external/chromium/sdch/open-vcdiff/src/
addrcache.h 32 // efficient reuse of one of the last four referenced addresses
33 // plus a small offset, and the "same" cache allows efficient reuse
  /external/chromium_org/sdch/open-vcdiff/src/
addrcache.h 32 // efficient reuse of one of the last four referenced addresses
33 // plus a small offset, and the "same" cache allows efficient reuse
  /external/chromium_org/third_party/icu/source/tools/toolutil/
xmlparser.h 18 * Not conformant. Not efficient.
156 * A simple XML parser; it is neither efficient nor conformant and only useful for
  /external/chromium_org/third_party/skia/src/core/
SkTSort.h 96 * specialize SkTSwap if T has an efficient swap operation.
185 * sure to specialize SkTSwap if T has an efficient swap operation.
  /external/chromium_org/third_party/tlslite/tlslite/utils/
keyfactory.py 208 and return the most efficient key possible.
216 Create a new private key. Return the most efficient key possible.
  /external/chromium_org/ui/surface/
accelerated_surface_transformer_win.h 141 // Efficient RGB->YV12 in two passes, but requires a device capable of writing
154 // Slower, less efficient RGB->YV12; does not require the device to have
  /external/clang/utils/TableGen/
TableGen.cpp 110 "Generate efficient matchers for HTML tag "
114 "Generate efficient matchers for HTML tag "
  /external/icu4c/tools/toolutil/
xmlparser.h 18 * Not conformant. Not efficient.
156 * A simple XML parser; it is neither efficient nor conformant and only useful for
  /external/open-vcdiff/src/
addrcache.h 32 // efficient reuse of one of the last four referenced addresses
33 // plus a small offset, and the "same" cache allows efficient reuse
  /external/proguard/docs/manual/
introduction.html 18 code base smaller, more efficient, and harder to reverse-engineer. The final
25 efficient use in Java 6.
  /external/skia/src/core/
SkTSort.h 96 * specialize SkTSwap if T has an efficient swap operation.
185 * sure to specialize SkTSwap if T has an efficient swap operation.
  /frameworks/base/graphics/java/android/renderscript/
Font.java 43 * are transparent to the user, they do happen internally, and it is more efficient to
44 * render large batches of text in sequence. It is also more efficient to render multiple
  /frameworks/base/docs/html/training/articles/
perf-tips.jd 34 <p>There are two basic rules for writing efficient code:</p>
53 your code is efficient at all levels and agressively optimize your performance.</p>
90 are also a <strong>lot</strong> more efficient than an array of {@code (int,int)}
99 code, you should try and be as efficient as possible.)</li>
354 isn't necessarily more efficient than programming with the
385 efficient. (So, for example, it was cheaper to invoke methods on a
  /prebuilts/python/darwin-x86/2.7.5/lib/python2.7/
heapq.py 44 The strange invariant above is meant to be an efficient memory
63 To be more memory efficient, when a winner is promoted, we try to
90 are more efficient overall, yet the worst cases might be terrible.
159 This is more efficient than heappop() followed by heappush(), and can be
287 # 2198, 2148, and 2219 compares: heapify() is more efficient, when
292 # heappop() compares): list.sort() is (unsurprisingly!) more efficient

Completed in 1605 milliseconds

1 2 3 4 5 6 78 91011>>