HomeSort by relevance Sort by last modified time
    Searched full:efficient (Results 76 - 100 of 2346) sorted by null

1 2 34 5 6 7 8 91011>>

  /external/chromium_org/third_party/re2/re2/
unicode_casefold.h 36 // The grouped form also allows for efficient fold range calculations
  /external/chromium_org/third_party/skia/src/core/
SkBBoxHierarchy.h 35 * bounding boxes, and allows efficient retrieval of intersections with query rectangles.
  /external/chromium_org/tools/cr/cr/actions/
runner.py 66 Do not call the base version if you implement a more efficient one.
  /external/chromium_org/v8/test/webkit/
regexp-non-bmp-expected.txt 24 Tests that regular expressions treat non-BMP characters as two separate characters. From a Unicode correctness point of view this is wrong, but it is what other browsers do. And given that we store strings as UTF-16, it is also more efficient to implement. Also test some other cases related to UTF-8 and UTF-16.
regexp-non-bmp.js 27 + 'And given that we store strings as UTF-16, it is also more efficient to implement. '
  /external/clang/include/clang/AST/
DeclAccessPair.h 11 // efficient representation of a pair of a NamedDecl* and an
  /external/clang/include/clang/Rewrite/Core/
DeltaTree.h 22 /// features. B-Trees are generally more memory and cache efficient than
  /external/dropbear/libtommath/
bn_mp_dr_reduce.c 22 * "Generating Efficient Primes for Discrete Log Cryptosystems"
  /external/guava/guava/src/com/google/common/collect/
HashMultiset.java 59 * <p>This implementation is highly efficient when {@code elements} is itself
  /external/guava/guava-gwt/src-super/com/google/common/collect/super/com/google/common/collect/
LinkedHashMultiset.java 61 * <p>This implementation is highly efficient when {@code elements} is itself
  /external/hamcrest/src/org/hamcrest/
BaseDescription.java 89 * Override in subclasses to provide an efficient implementation.
  /external/kernel-headers/original/asm-generic/
local.h 44 * much more efficient than these naive implementations. Note they take
  /external/llvm/lib/IR/
ConstantsContext.h 66 /// Transparently provide more efficient getOperand methods.
86 /// Transparently provide more efficient getOperand methods.
107 /// Transparently provide more efficient getOperand methods.
129 /// Transparently provide more efficient getOperand methods.
154 /// Transparently provide more efficient getOperand methods.
180 /// Transparently provide more efficient getOperand methods.
207 /// Transparently provide more efficient getOperand methods.
228 /// Transparently provide more efficient getOperand methods.
250 /// Transparently provide more efficient getOperand methods.
  /external/llvm/test/DebugInfo/AArch64/
cfi-frame.ll 17 ; Make sure the prologue is reasonably efficient
  /external/objenesis/main/src/org/objenesis/
ObjenesisBase.java 78 * instances from the same class, it is way more efficient to create them from the same
ObjenesisHelper.java 59 * instances from the same class, it is way more efficient to create them from the same
  /external/okhttp/src/main/java/com/squareup/okhttp/internal/http/
Transport.java 30 * forgotten. This is most efficient, particularly for large request
  /external/proguard/docs/manual/
wtk.html 19 up to date and it solves some problems. It is also somewhat more efficient,
  /external/regex-re2/re2/
unicode_casefold.h 36 // The grouped form also allows for efficient fold range calculations
  /external/skia/src/core/
SkBBoxHierarchy.h 35 * bounding boxes, and allows efficient retrieval of intersections with query rectangles.
  /external/srec/srec/clib/
memmove.h 34 ** A more efficient implementation of memmove
  /frameworks/base/docs/html/guide/practices/app-design/
index.jd 18 <li><a href="performance.html">Designing for Performance</a> (writing efficient Android code)</a></li>
  /frameworks/base/docs/html/training/basics/network-ops/
index.jd 25 <li><a href="{@docRoot}training/efficient-downloads/index.html">Transferring Data Without Draining the Battery</a></li>
  /frameworks/base/docs/html/training/improving-layouts/
index.jd 48 shows you how to create efficient, re-usable layout constructs, then include them in the appropriate
optimizing-layout.jd 37 <p>It is a common misconception that using the basic layout structures leads to the most efficient
140 <li>Merge root frame - If a {@link android.widget.FrameLayout} is the root of a layout and does not provide background or padding etc, it can be replaced with a merge tag which is slightly more efficient.</li>
141 <li>Useless leaf - A layout that has no children or no background can often be removed (since it is invisible) for a flatter and more efficient layout hierarchy.</li>
142 <li>Useless parent - A layout with children that has no siblings, is not a {@link android.widget.ScrollView} or a root layout, and does not have a background, can be removed and have its children moved directly into the parent for a flatter and more efficient layout hierarchy.</li>

Completed in 3654 milliseconds

1 2 34 5 6 7 8 91011>>