HomeSort by relevance Sort by last modified time
    Searched refs:these (Results 126 - 150 of 253) sorted by null

1 2 3 4 56 7 8 91011

  /external/libvorbis/doc/
06-floor0.tex 40 An end-of-packet condition during any of these bitstream reads renders
07-floor1.tex 243 iterative prediction to find final Y values, these points are
04-codec.tex 38 (these types are all odd as a packet with a leading single bit of '0'
69 meet any of these conditions renders a stream undecodable.
122 These hooks are placeholders in Vorbis I. Nevertheless, the
614 These channel orderings refer to order within the encoded stream. It
  /external/v8/benchmarks/
base.js 36 // running the benchmark, but the running time of these functions will
  /external/v8/test/mjsunit/
array-functions-prototype-misc.js 30 * and large arrays. Some of these methods are specified such that they
elements-kind.js 311 // DOUBLE->OBJECT, and SMI->OBJECT. No matter in which order these three are
function-call.js 74 // or null as this we still explicitly test that we throw on these here.
mirror-object.js 89 // If the object has some special properties don't test for these.
  /external/v8/test/perf-test/Collections/
base.js 24 // running the benchmark, but the running time of these functions will
  /external/v8/test/webkit/fast/js/
parser-syntax-check.js 175 // Note these are tested elsewhere, no need to repeat those tests here
  /frameworks/rs/api/
rs_for_each.spec 23 an executing kernel, like dimensions and current indexes. These functions take
179 &nbsp;&nbsp;// adding these variables as arguments. For the more rarely used indexes<br/>
  /art/test/
Android.run-test.mk 294 # All these tests check that we have sane behavior if we don't have a patchoat or dex2oat.
295 # Therefore we shouldn't run them in situations where we actually don't have these since they
296 # explicitly test for them. These all also assume we have an image.
353 # TODO: Find a way to run these tests in ndebug mode.
    [all...]
  /external/bison/build-aux/
texinfo.tex     [all...]
  /external/libvpx/libvpx/vp9/common/arm/neon/
vp9_idct32x32_add_neon.asm 11 ;TODO(cd): adjust these constant to be able to use vqdmulh for faster
679 ; TODO(cd) do some register allocation change to remove these push/pop
696 ; TODO(cd) do some register allocation change to remove these push/pop
    [all...]
  /external/v8/src/
v8natives.js     [all...]
runtime.js 8 // directly from compiled code. These are the functions with names in
11 // cannot use contexts in all these functions.
  /hardware/intel/common/omx-components/videocodec/libvpx_internal/libvpx/vp9/common/arm/neon/
vp9_idct32x32_add_neon.asm 11 ;TODO(cd): adjust these constant to be able to use vqdmulh for faster
679 ; TODO(cd) do some register allocation change to remove these push/pop
696 ; TODO(cd) do some register allocation change to remove these push/pop
    [all...]
  /external/antlr/antlr-3.4/runtime/Delphi/Sources/Antlr3.Runtime/
Antlr.Runtime.Tree.pas 159 /// constructing these nodes so we should have this control for
429 /// such as CommonTreeNodeStream that work on these kinds of trees. You
608 /// Better to spend the space in every tree node. If you don't want these
    [all...]
  /external/compiler-rt/make/platform/
clang_darwin.mk 0 # These are the functions which clang needs when it is targeting a previous
91 # Configuration for targeting OSX. These functions may not be in libSystem
161 # Always set deployment target arguments for every build, these libraries should
  /external/libunwind/doc/
libunwind-ia64.tex 121 general (integer) registers. A non-zero value in these registers
  /external/strace/
strace.spec 452 - version 4.2 (why are we keeping all these patches around?)
  /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...]
  /prebuilts/python/linux-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...]
  /external/dnsmasq/contrib/dnslist/
dnslist.pl 294 in new free programs; and that you know you can do these things.
297 anyone to deny you these rights or to ask you to surrender the rights.
298 These restrictions translate to certain responsibilities for you if you
304 source code. And you must show them these terms so they know their
361 above, provided that you also meet all of these conditions:
377 these conditions, and telling the user how to view a copy of this
382 These requirements apply to the modified work as a whole. If
450 distribute the Program or its derivative works. These actions are
460 these terms and conditions. You may not impose any further
550 How to Apply These Terms to Your New Program
    [all...]
  /external/libvncserver/x11vnc/misc/enhanced_tightvnc_viewer/bin/util/
ssvnc.tcl 190 something like one of these:
340 these programs must be available in $PATH on the remote server when
370 See these links for more information:
799 Prefix any of these files with "FORCE:" to make them immutable.
812 See also these links for more information:
847 that other users can log into and you DO NOT TRUST these users
861 another service, e.g. CUPS printing). These are the stunnel(8) SSL
864 running SSVNC can connect to these ports, however this includes any
867 If the untrusted local user tries to connect to these ports, he ma
    [all...]

Completed in 3839 milliseconds

1 2 3 4 56 7 8 91011