/external/jpeg/ |
jpegtran.1 | 112 For practical use, you may prefer to discard any untransformable edge pixels
|
usage.doc | 9 If you are on a Unix machine you may prefer to read the Unix-style manual 50 have pipes. (You can get this style on Unix too, if you prefer, by defining 459 For practical use, you may prefer to discard any untransformable edge pixels
|
/external/libvpx/libvpx/third_party/googletest/src/cmake/ |
internal_utils.cmake | 38 # We prefer more strict warning checking for building Google Test.
|
/external/llvm/docs/ |
ReleaseNotes.rst | 10 prefer the `LLVM 3.2 Release Notes <http://llvm.org/releases/3.2/docs
|
CodingStandards.rst | 132 In general, prefer C++ style (``//``) comments. They take less space, require 278 listed. We prefer these ``#include``\s to be listed in this order: 322 In all cases, prefer spaces to tabs in source files. People have different 719 of this sort of loop, we strongly prefer to use a predicate function (which may 720 be `static`_) that uses `early exits`_ to compute the predicate. We prefer the [all...] |
/external/llvm/lib/CodeGen/ |
CalcSpillWeights.cpp | 177 // Always prefer the physreg hint.
|
/external/llvm/lib/Target/X86/ |
README-FPStack.txt | 7 Some targets (e.g. athlons) prefer freep to fstp ST(0):
|
/external/okhttp/src/main/java/com/squareup/okhttp/internal/http/ |
RouteSelector.java | 98 // Always prefer pooled connections over new connections.
|
/external/protobuf/src/google/protobuf/stubs/ |
substitute.h | 102 // prefer an integer representation. But, we don't really know. So, we
|
/external/protobuf/vsprojects/ |
readme.txt | 3 we prefer to develop under a Unix-like environment -- but it may be more
|
/external/qemu/distrib/jpeg-6b/ |
jerror.c | 89 * Most Windows applications will still prefer to override this routine,
|
jpegtran.1 | 112 For practical use, you may prefer to discard any untransformable edge pixels
|
usage.doc | 9 If you are on a Unix machine you may prefer to read the Unix-style manual 50 have pipes. (You can get this style on Unix too, if you prefer, by defining 459 For practical use, you may prefer to discard any untransformable edge pixels
|
/external/regex-re2/re2/testing/ |
unicode_test.py | 181 # prefer category Nd over N
|
/external/srec/tools/thirdparty/OpenFst/fst/lib/ |
compose.h | 672 // - the choice of which tnansducer is sorted - prefer sorting the FST 677 // the input side of the second transducer or prefer placing 889 // - the choice of which tnansducer is sorted - prefer sorting the FST 894 // the input side of the second transducer or prefer placing [all...] |
/frameworks/av/cmds/stagefright/ |
recordvideo.cpp | 46 fprintf(stderr, " -s(oftware) prefer software codec\n");
|
/frameworks/base/docs/html/guide/topics/manifest/ |
intent-filter-element.jd | 116 which the broadcasts are received, or want to force Android to prefer
|
/frameworks/base/policy/src/com/android/internal/policy/impl/keyguard/ |
KeyguardAccountView.java | 210 * the stored account that they probably intended. Prefer, in order:
|
/frameworks/base/test-runner/src/android/test/ |
ActivityInstrumentationTestCase2.java | 39 * <p>If you prefer an isolated unit test, see {@link android.test.ActivityUnitTestCase}.
|
/hardware/qcom/display/liblight/ |
lights.c | 192 // Prefer RGB LEDs, fallback to white LED
|
/packages/apps/Browser/src/com/android/browser/ |
BrowserBackupAgent.java | 56 * This simply preserves the existing state as we now prefer Chrome Sync
|
/packages/apps/Contacts/src/com/android/contacts/quickcontact/ |
ResolveCache.java | 181 // Accept any package from prefer list, otherwise first system app
|
/packages/apps/Settings/src/com/android/settings/inputmethod/ |
InputMethodPreference.java | 300 // Prefer always checked system IMEs
|
/external/stressapptest/src/ |
os.cc | 433 logprintf(3, "Log: Prefer POSIX shared memory allocation.\n"); 438 logprintf(3, "Log: Prefer using hugepace allocation.\n"); 440 logprintf(3, "Log: Prefer plain malloc memory allocation.\n");
|
/packages/inputmethods/PinyinIME/jni/include/ |
matrixsearch.h | 52 // in this mode, there is no clear boundaries, we prefer those results which 131 // If it is true, the engine will prefer long history based prediction, 132 // for example, when user inputs "BeiJing", we prefer "DaXue", etc., which are
|