/external/chromium_org/ui/file_manager/file_manager/foreground/js/ |
file_tasks.js | 126 * The list of known extensions to record UMA.
|
/external/iproute2/doc/ |
api-ip6-flowlabels.tex | 126 before filling known fields is robust but stupid solution.
|
/external/libunwind/doc/ |
libunwind.tex | 113 (IP), sometimes also known as the ``program counter'', and the stack
|
/external/mesa3d/docs/ |
MESA_texture_array.spec | 15 No known IP issues. [all...] |
/external/zlib/src/contrib/masmx86/ |
match686.asm | 18 ; (and the faster known version of match_init on modern Core 2 Duo and AMD Phenom)
|
/ndk/build/core/ |
init.mk | 527 # the list of known abis and archs
|
/external/chromium_org/v8/test/mjsunit/ |
unicode-test.js | [all...] |
/external/chromium_org/chrome/browser/resources/profiler/ |
profiler.js | 121 // speeds up the property accesses a bit. The following keys are well-known [all...] |
/external/blktrace/btreplay/doc/ |
btreplay.tex | 180 \newpage\subsection{Known Deficiencies and Proposed Possible Fixes} 182 The overall known deficiencies with this current set of utilities is
|
/external/chromium_org/chrome/browser/resources/options/chromeos/ |
display_options.js | 51 * @param {HTMLElement} element The element to be known. [all...] |
/external/chromium_org/ppapi/native_client/tools/browser_tester/browserdata/ |
nacltest.js | 368 // Arrays should do this automatically, but there is a known bug where
|
/external/chromium_org/third_party/libvpx/source/libvpx/third_party/libyuv/source/ |
x86inc.asm | 783 ; Append cpuflags to the callee's name iff the appended name is known and the plain name isn't
|
/external/chromium_org/third_party/libvpx/source/libvpx/third_party/x86inc/ |
x86inc.asm | 893 ; Append cpuflags to the callee's name iff the appended name is known and the plain name isn't
|
/external/chromium_org/third_party/libyuv/source/ |
x86inc.asm | 783 ; Append cpuflags to the callee's name iff the appended name is known and the plain name isn't
|
/external/chromium_org/third_party/skia/gm/rebaseline_server/static/new/js/ |
app.js | 113 // backend to reflect the current "known" image sets to compare. [all...] |
/external/chromium_org/tools/binary_size/template/ |
D3SymbolTreeMap.js | 109 * of that symbol type. If the symbol type does not match one of the known [all...] |
/external/libvorbis/doc/ |
01-introduction.tex | 219 modern use. No known Vorbis encoder past Xiph.org's own beta 4 makes
|
/external/libvpx/libvpx/third_party/x86inc/ |
x86inc.asm | 872 ; Append cpuflags to the callee's name iff the appended name is known and the plain name isn't
|
/hardware/intel/common/omx-components/videocodec/libvpx_internal/libvpx/third_party/x86inc/ |
x86inc.asm | 872 ; Append cpuflags to the callee's name iff the appended name is known and the plain name isn't
|
/frameworks/base/services/core/java/com/android/server/pm/ |
PackageManagerService.java | 423 // Currently known shared libraries. 5358 PackageSetting known = mSettings.peekPackageLPr(pkg.packageName); local [all...] |
/dalvik/docs/ |
prettify.js | 536 * a known character. Must have a shortcut string. [all...] |
/external/libunwind/aux/ |
ltmain.sh | [all...] |
/prebuilts/devtools/tools/lib/ |
sdk-common.jar | |
/prebuilts/gradle-plugin/com/android/tools/sdk-common/22.2.0/ |
sdk-common-22.2.0.jar | |
/prebuilts/python/darwin-x86/2.7.5/lib/python2.7/pydoc_data/ |
topics.py | 9 'binary': '\nBinary arithmetic operations\n****************************\n\nThe binary arithmetic operations have the conventional priority\nlevels. Note that some of these operations also apply to certain non-\nnumeric types. Apart from the power operator, there are only two\nlevels, one for multiplicative operators and one for additive\noperators:\n\n m_expr ::= u_expr | m_expr "*" u_expr | m_expr "//" u_expr | m_expr "/" u_expr\n | m_expr "%" u_expr\n a_expr ::= m_expr | a_expr "+" m_expr | a_expr "-" m_expr\n\nThe ``*`` (multiplication) operator yields the product of its\narguments. The arguments must either both be numbers, or one argument\nmust be an integer (plain or long) and the other must be a sequence.\nIn the former case, the numbers are converted to a common type and\nthen multiplied together. In the latter case, sequence repetition is\nperformed; a negative repetition factor yields an empty sequence.\n\nThe ``/`` (division) and ``//`` (floor division) operators yield the\nquotient of their arguments. The numeric arguments are first\nconverted to a common type. Plain or long integer division yields an\ninteger of the same type; the result is that of mathematical division\nwith the \'floor\' function applied to the result. Division by zero\nraises the ``ZeroDivisionError`` exception.\n\nThe ``%`` (modulo) operator yields the remainder from the division of\nthe first argument by the second. The numeric arguments are first\nconverted to a common type. A zero right argument raises the\n``ZeroDivisionError`` exception. The arguments may be floating point\nnumbers, e.g., ``3.14%0.7`` equals ``0.34`` (since ``3.14`` equals\n``4*0.7 + 0.34``.) The modulo operator always yields a result with\nthe same sign as its second operand (or zero); the absolute value of\nthe result is strictly smaller than the absolute value of the second\noperand [2].\n\nThe integer division and modulo operators are connected by the\nfollowing identity: ``x == (x/y)*y + (x%y)``. Integer division and\nmodulo are also connected with the built-in function ``divmod()``:\n``divmod(x, y) == (x/y, x%y)``. These identities don\'t hold for\nfloating point numbers; there similar identities hold approximately\nwhere ``x/y`` is replaced by ``floor(x/y)`` or ``floor(x/y) - 1`` [3].\n\nIn addition to performing the modulo operation on numbers, the ``%``\noperator is also overloaded by string and unicode objects to perform\nstring formatting (also known as interpolation). The syntax for string\nformatting is described in the Python Library Reference, section\n*String Formatting Operations*.\n\nDeprecated since version 2.3: The floor division operator, the modulo\noperator, and the ``divmod()`` function are no longer defined for\ncomplex numbers. Instead, convert to a floating point number using\nthe ``abs()`` function if appropriate.\n\nThe ``+`` (addition) operator yields the sum of its arguments. The\narguments must either both be numbers or both sequences of the same\ntype. In the former case, the numbers are converted to a common type\nand then added together. In the latter case, the sequences are\nconcatenated.\n\nThe ``-`` (subtraction) operator yields the difference of its\narguments. The numeric arguments are first converted to a common\ntype.\n', [all...] |