OpenGrok
Home
Sort by relevance
Sort by last modified time
Full Search
Definition
Symbol
File Path
History
|
|
Help
Searched
refs:described
(Results
1 - 25
of
58
) sorted by null
1
2
3
/development/tools/line_endings/
Android.mk
3
# Copies files into the directory structure
described
by a manifest
/build/tools/atree/
Android.mk
3
# Copies files into the directory structure
described
by a manifest
/frameworks/base/tools/aidl/
Android.mk
3
# Copies files into the directory structure
described
by a manifest
/external/chromium_org/v8/test/promises-aplus/lib/
mocha.js
171
function TestSuite(
described
) {
172
this.description =
described
.description;
177
if (
described
.before) {
179
described
.before, undefined, false));
181
for (var i = 0; i <
described
.cases.length; ++i) {
182
this.cases.push(new TestCase(
described
.cases[i].description,
183
described
.beforeEach,
184
described
.cases[i].fn,
185
described
.afterEach,
188
if (
described
.after)
[
all
...]
/external/chromium_org/remoting/tools/win/
chromoting-set-channel.bat
10
REM Based on method
described
at:
/external/chromium_org/third_party/yasm/source/patched-yasm/modules/objfmts/win64/tests/
sce1.asm
33
; this isn't part of the official epilog, as
described
in section 2.5
sce3.asm
33
; this isn't part of the official epilog, as
described
in section 2.5
/external/libunwind/doc/
_U_dyn_register.tex
21
described
by a structure of type \Type{unw\_dyn\_info\_t} (see
libunwind-dynamic.tex
61
The only point in the epilogue that needs to be
described
explicitly
63
gets restored. The reason this point needs to be
described
is that
72
fashion needs to be
described
with an operation descriptor. For this
90
\Type{unw\_dyn\_info\_t} structure are
described
below:
121
The format of these sub-members is
described
in detail below.
128
the details of a procedure are
described
by a structure of type
165
is
described
by a structure of type \Type{unw\_dyn\_table\_info}.
246
prologue, the body, and a canned epilogue. This could be
described
by
278
of the \Type{unw\_dyn\_operation\_t} values
described
below.
291
a value of 0 means that the effect
described
by this directiv
[
all
...]
unw_get_fpreg.tex
23
The register numbering is target-dependent and
described
in separate
unw_get_reg.tex
23
The register numbering is target-dependent and
described
in separate
unw_set_fpreg.tex
23
The register numbering is target-dependent and
described
in separate
unw_set_reg.tex
23
The register numbering is target-dependent and
described
in separate
/external/chromium_org/tools/telemetry/telemetry/core/
network_quiescence.js
55
* This method uses the Resource Timing interface, which is
described
at
/external/chromium_org/v8/test/webkit/fast/js/
regexp-ranges-and-escaped-hyphens.js
25
'Tests for bug <a href="https://bugs.webkit.org/show_bug.cgi?id=21232">#21232</a>, and related range issues
described
in bug.'
/external/valgrind/main/coregrind/m_debuginfo/
debuginfo.c
607
in. Returns a ULong whose purpose is
described
in comments
3194
XArray*
described
= ML_(describe_type)( &residual_offset,
local
3302
XArray*
described
= ML_(describe_type)( &residual_offset,
local
[
all
...]
/ndk/sources/host-tools/nawk-20071023/
README
25
This is the version of awk
described
in "The AWK Programming Language",
/external/chromium_org/third_party/mesa/src/docs/
MESA_texture_signed_rgba.spec
81
RESOLVED: Same as
described
in issue 5) of
115
and converting back (using the mapping
described
here).
125
RESOLVED: Same as
described
in issue 6) of
/external/mesa3d/docs/
MESA_texture_signed_rgba.spec
81
RESOLVED: Same as
described
in issue 5) of
115
and converting back (using the mapping
described
here).
125
RESOLVED: Same as
described
in issue 6) of
/external/chromium_org/third_party/mesa/src/docs/OLD/
MESA_packed_depth_stencil.spec
172
described
in the table below:
/external/mesa3d/docs/OLD/
MESA_packed_depth_stencil.spec
172
described
in the table below:
/external/libvorbis/doc/
01-introduction.tex
118
reference Vorbis decoder
described
below may be considered a proper
282
encoding and proper use of the comment header is
described
in \xref{vorbis:spec:comment}.
320
of the three Vorbis headers
described
above. The fourth packet type
336
as
described
earlier, all of which may be used in a given Vorbis
401
or angle. The coupling relationships are
described
in the codec setup
08-residue.tex
352
Format zero decodes partitions exactly as
described
earlier in the
386
Format 1 decodes partitions exactly as
described
earlier in the
431
\item Post decode: Deinterleave the single vector \varname{[v]} returned by format 1 decode as
described
above into \emph{ch} independent vectors, one for each outputchannel, according to:
/external/valgrind/main/none/tests/
cmdline1.stdout.exp
43
--suppressions=<filename> suppress errors
described
in <filename>
/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
...]
Completed in 381 milliseconds
1
2
3