Home
last modified time | relevance | path

Searched refs:are (Results 1 – 25 of 5674) sorted by relevance

12345678910>>...227

/external/chromium_org/tools/clang/plugins/tests/
Dbase_refcounted.txt2 …nted.h:47:3: warning: [chromium-style] Classes that are ref-counted should have destructors that a…
8 …nted.h:59:3: warning: [chromium-style] Classes that are ref-counted should have destructors that a…
14 ./base_refcounted.h:73:3: warning: [chromium-style] Classes that are ref-counted and have non-priva…
17 …ted.h:110:3: warning: [chromium-style] Classes that are ref-counted should have destructors that a…
26 …h:115:7: warning: [chromium-style] Classes that are ref-counted should have explicit destructors t…
35 …ted.h:145:1: warning: [chromium-style] Classes that are ref-counted should have destructors that a…
47 …h:164:1: warning: [chromium-style] Classes that are ref-counted should have explicit destructors t…
59 ./base_refcounted.h:204:3: warning: [chromium-style] Classes that are ref-counted and have non-priv…
62 ./base_refcounted.h:204:3: warning: [chromium-style] Classes that are ref-counted and have non-priv…
63 …ed.cpp:16:3: warning: [chromium-style] Classes that are ref-counted should have destructors that a…
[all …]
/external/llvm/lib/Target/Mips/
DMipsCallingConv.td20 // Only the return rules are defined here for O32. The rules for argument
21 // passing are defined in MipsISelLowering.cpp.
23 // i32 are returned in registers V0, V1, A0, A1
26 // f32 are returned in registers F0, F2
29 // f64 are returned in register D0, D1
41 // Integer arguments are passed in integer registers.
52 // f32 arguments are passed in single precision FP registers.
58 // f64 arguments are passed in double precision FP registers.
64 // All stack parameter slots become 64-bit doublewords and are 8-byte aligned.
70 // All arguments are passed in integer registers.
[all …]
/external/clang/test/SemaObjC/
Dproperty-10.m6 …int p0; // expected-error {{property attributes 'readonly' and 'readwrite' are mutually exclusive}}
13 @property(assign, copy) id p3_0; // expected-error {{property attributes 'assign' and 'copy' are mu…
14 …in) id p3_1; // expected-error {{property attributes 'assign' and 'retain' are mutually exclusive}…
15 …ng) id s3_1; // expected-error {{property attributes 'assign' and 'strong' are mutually exclusive}…
16 @property(copy, retain) id p3_2; // expected-error {{property attributes 'copy' and 'retain' are mu…
17 @property(copy, strong) id s3_2; // expected-error {{property attributes 'copy' and 'strong' are mu…
18 … attributes 'assign' and 'copy' are mutually exclusive}}, expected-error {{property attributes 'as…
19 … attributes 'assign' and 'copy' are mutually exclusive}}, expected-error {{property attributes 'as…
21 …_0; // expected-error {{property attributes 'unsafe_unretained' and 'copy' are mutually exclusive}…
22 …; // expected-error {{property attributes 'unsafe_unretained' and 'retain' are mutually exclusive}…
[all …]
Dproperty-12.m4 …n) id X; // expected-warning {{property attributes 'readonly' and 'assign' are mutually exclusive}}
8 …n) id X; // expected-warning {{property attributes 'readonly' and 'retain' are mutually exclusive}}
12 @property(readonly,copy) id X; // expected-warning {{property attributes 'readonly' and 'copy' are …
16 …) id X; // expected-error {{property attributes 'readonly' and 'readwrite' are mutually exclusive}}
20 @property(assign,copy) id X; // expected-error {{property attributes 'assign' and 'copy' are mutual…
24 @property(assign,retain) id X; // expected-error {{property attributes 'assign' and 'retain' are mu…
28 @property(copy,retain) id X; // expected-error {{property attributes 'copy' and 'retain' are mutual…
/external/valgrind/main/none/tests/s390x/
Dtroo.stdout.exp2 the translated values are
4 the translated values are
6 the translated values are ff bb dd ab ca
8 the translated values are ff bb dd ab ca bc cc da ea aa
10 the translated values are
12 the translated values are ff
14 the translated values are ff bb dd ab ca bc cc da
Dop_exception.stderr.exp6 did not recognise. There are two possible reasons for this.
8 location. If you are running Memcheck and you just saw a
12 you are not sure, please let us know and we'll try to fix it.
19 did not recognise. There are two possible reasons for this.
21 location. If you are running Memcheck and you just saw a
25 you are not sure, please let us know and we'll try to fix it.
32 did not recognise. There are two possible reasons for this.
34 location. If you are running Memcheck and you just saw a
38 you are not sure, please let us know and we'll try to fix it.
45 did not recognise. There are two possible reasons for this.
[all …]
/external/valgrind/main/memcheck/tests/
Dleak-delta.stderr.exp2 10 bytes in 1 blocks are still reachable in loss record ... of ...
9 10 (+10) bytes in 1 (+1) blocks are definitely lost in loss record ... of ...
14 21 (+21) bytes in 1 (+1) blocks are still reachable in loss record ... of ...
20 65 (+65) bytes in 2 (+2) blocks are still reachable in loss record ... of ...
27 10 (+10) bytes in 1 (+1) blocks are still reachable in loss record ... of ...
33 0 (-10) bytes in 0 (-1) blocks are still reachable in loss record ... of ...
38 10 (+10) bytes in 1 (+1) blocks are definitely lost in loss record ... of ...
44 0 (-10) bytes in 0 (-1) blocks are definitely lost in loss record ... of ...
49 10 (+10) bytes in 1 (+1) blocks are still reachable in loss record ... of ...
55 32 (+32) bytes in 1 (+1) blocks are definitely lost in loss record ... of ...
[all …]
Dleak-cases-full.stderr.exp5 16 bytes in 1 blocks are possibly lost in loss record ... of ...
11 16 bytes in 1 blocks are possibly lost in loss record ... of ...
17 16 bytes in 1 blocks are possibly lost in loss record ... of ...
23 16 bytes in 1 blocks are possibly lost in loss record ... of ...
29 16 bytes in 1 blocks are possibly lost in loss record ... of ...
35 16 bytes in 1 blocks are possibly lost in loss record ... of ...
41 16 bytes in 1 blocks are definitely lost in loss record ... of ...
47 32 (16 direct, 16 indirect) bytes in 1 blocks are definitely lost in loss record ... of ...
53 32 (16 direct, 16 indirect) bytes in 1 blocks are definitely lost in loss record ... of ...
/external/valgrind/main/gdbserver_tests/
Dmcleak.stderrB.exp3 10 bytes in 1 blocks are still reachable in loss record ... of ...
8 10 (+10) bytes in 1 (+1) blocks are definitely lost in loss record ... of ...
13 21 (+21) bytes in 1 (+1) blocks are still reachable in loss record ... of ...
18 65 (+65) bytes in 2 (+2) blocks are still reachable in loss record ... of ...
23 10 (+10) bytes in 1 (+1) blocks are still reachable in loss record ... of ...
28 0 (-10) bytes in 0 (-1) blocks are still reachable in loss record ... of ...
33 10 (+10) bytes in 1 (+1) blocks are definitely lost in loss record ... of ...
38 0 (-10) bytes in 0 (-1) blocks are definitely lost in loss record ... of ...
43 10 (+10) bytes in 1 (+1) blocks are still reachable in loss record ... of ...
48 32 (+32) bytes in 1 (+1) blocks are definitely lost in loss record ... of ...
[all …]
/external/chromium_org/v8/test/webkit/fast/js/
Dnumeric-escapes-in-string-literals-expected.txt5 # modification, are permitted provided that the following conditions
6 # are met:
32 PASS eval(stringLiteral) threw exception SyntaxError: Octal literals are not allowed in strict mode…
34 PASS eval(stringLiteral) threw exception SyntaxError: Octal literals are not allowed in strict mode…
40 PASS eval(stringLiteral) threw exception SyntaxError: Octal literals are not allowed in strict mode…
42 PASS eval(stringLiteral) threw exception SyntaxError: Octal literals are not allowed in strict mode…
44 PASS eval(stringLiteral) threw exception SyntaxError: Octal literals are not allowed in strict mode…
46 PASS eval(stringLiteral) threw exception SyntaxError: Octal literals are not allowed in strict mode…
48 PASS eval(stringLiteral) threw exception SyntaxError: Octal literals are not allowed in strict mode…
50 PASS eval(stringLiteral) threw exception SyntaxError: Octal literals are not allowed in strict mode…
[all …]
/external/llvm/docs/
DLLVMBuild.rst22 as to how the source code and various components are organized. The
23 ``LLVMBuild.txt`` files are the explicit specification of that
24 structure, and are used by the build systems and other tools in order to
36 For the most part, the project contents are organized around defining
40 The component descriptions for the project as a whole are automatically
50 The LLVMBuild files themselves are just a declarative way to describe
62 Developers generally are not expected to need to be aware of the details
64 LLVM developers who are not working on the build system would only ever
75 As mentioned earlier, LLVM projects are organized into logical
87 - *Build Tools* - Build tools are applications which are designed to be run
[all …]
/external/antlr/antlr-3.4/antlr3-maven-plugin/src/site/apt/
Dindex.apt11 The ANTLR v3 Maven plugin is completely re-written as of version 3.1.3; if you are familiar
12 with prior versions, you should note that there are some behavioral differences that make
16 input grammar files are and where the output files should be generated. As with all Maven
17 plugins, there are defaults, which you are advised to comply to, but are not forced to
21 options that are useful for a build system. The code required to calculate dependencies,
31 You may also find that there are patch versions of the plugin suchas 3.1.3-1 3.1.3-2 and
49 +--- imports/ .g files that are imported by other grammars.
55 When the Java files are compiled they will be in the correct location for the javac
56 compiler without any special configuration. The generated java files are automatically
60 any grammar files that are imported by other grammar files (do not make subdirectories here.)
[all …]
/external/llvm/lib/Target/Sparc/
DSparcCallingConv.td23 // f64 arguments are split and passed through registers or through stack.
26 // Alternatively, they are assigned to the stack in 4-byte aligned units.
43 // occupy a multiple of 8 bytes in the array. Integer arguments are extended to
44 // 64 bits by the caller. Floats are right-aligned in their 8-byte slot, the
45 // first 4 bytes in the slot are undefined.
48 // array at fixed offsets. Integer arguments are promoted to registers when
52 // parameter array at fixed offsets. Float and double parameters are promoted
55 // Structs up to 16 bytes in size are passed by value. They are right-aligned
56 // in one or two 8-byte slots in the parameter array. Struct members are
81 // Two ints in a struct are simply coerced to i64:
[all …]
/external/chromium_org/chrome/common/extensions/docs/
DREADME7 Documentation for apps and extensions are partly generated from API definitions
10 All documentation sources are checked into source control, just like any other
14 The goals of this system are:
16 * Docs are generated from API definitions; it isn't possible to add or modify
19 * Docs are editable by anyone with Chrome commit access. This encourages
26 * Docs are branched automatically with Chrome's source code; the docs for each
27 Chrome release are kept with the corresponding source code.
30 /trunk/extensions/, /beta/apps/, etc.). These URLs are updated automatically
39 - If you are not updating the static HTML for a docs page, you will most
45 Chances are you'll want to change a file in either "intros" (if changing
[all …]
/external/llvm/lib/Target/X86/
DX86CallingConv.td25 // Scalar values are returned in AX first, then DX. For i8, the ABI
30 // for functions that return two i8 values are currently expected to pack the
40 // Vector types are returned in XMM0 and XMM1, when they fit. XMM2 and XMM3
46 // 256-bit vectors are returned in YMM0 and XMM1, when they fit. YMM2 and YMM3
52 // 512-bit vectors are returned in ZMM0 and ZMM1, when they fit. ZMM2 and ZMM3
58 // MMX vector types are always returned in MM0. If the target doesn't have
62 // Long double types are always returned in ST0 (even with SSE).
99 // Vector types are returned in XMM0,XMM1,XMMM2 and XMM3.
131 // MMX vector types are always returned in XMM0.
205 // The first 6 integer arguments are passed in integer registers.
[all …]
/external/libppp/src/
DREADME.changes6 modification, are permitted provided that the following conditions
7 are met:
49 diagnostic connections are dropped.
52 o Errors in `add' and `delete' are logged as warnings rather than being
54 o Any number of diagnostic prompts are allowed, and they are allowed in
61 o Out-of-sequence FSM packets (IPCP/LCP/CCP) are dropped by default.
62 o Reconnect values are used after an LQR timeout.
72 o Filters are now called `allow', `dial', `in' and `out'. `set
77 o Throughput statistics are enabled by default.
84 o `show auto', `show loopback' and `show mtu' are all part of `show bundle'.
[all …]
/external/jpeg/
Dwizard.doc6 The "wizard" switches are intended for experimentation with JPEG by persons
7 who are reasonably knowledgeable about the JPEG standard. If you don't know
8 what you are doing, DON'T USE THESE SWITCHES. You'll likely produce files
23 values are supported by the IJG software, this feature is not in baseline
28 size, since more bits than necessary are expended on higher AC coefficients.
37 The tables are implicitly numbered 0,1,etc. in order of appearance. Table
41 Quantization table files are free format, in that arbitrary whitespace can
69 are used exactly as-is. If both -qtables and -quality are used, then the
70 tables taken from the file are scaled in the same fashion that the default
72 the quantization values are constrained to the range 1-255.
[all …]
/external/qemu/distrib/jpeg-6b/
Dwizard.doc6 The "wizard" switches are intended for experimentation with JPEG by persons
7 who are reasonably knowledgeable about the JPEG standard. If you don't know
8 what you are doing, DON'T USE THESE SWITCHES. You'll likely produce files
23 values are supported by the IJG software, this feature is not in baseline
28 size, since more bits than necessary are expended on higher AC coefficients.
37 The tables are implicitly numbered 0,1,etc. in order of appearance. Table
41 Quantization table files are free format, in that arbitrary whitespace can
69 are used exactly as-is. If both -qtables and -quality are used, then the
70 tables taken from the file are scaled in the same fashion that the default
72 the quantization values are constrained to the range 1-255.
[all …]
/external/eigen/unsupported/doc/
DOverview.dox7 These modules are contributions from various users. They are provided "as is", without any support.
16 The unsupported modules are contributions from various users. They are
17 provided "as is", without any support. Nevertheless, some of them are
/external/chromium_org/third_party/mesa/src/docs/
DREADME.WIN329 Windows drivers are build with SCons. Makefiles or Visual Studio projects are
43 The DLL files are built so that the external entry points use the
46 Static LIB files are not built. The LIB files that are built with are
49 The si-glu sources are used to build the GLU libs. This was done
/external/mesa3d/docs/
DREADME.WIN329 Windows drivers are build with SCons. Makefiles or Visual Studio projects are
43 The DLL files are built so that the external entry points use the
46 Static LIB files are not built. The LIB files that are built with are
49 The si-glu sources are used to build the GLU libs. This was done
/external/chromium_org/mojo/public/
DREADME.md4 The Mojo Public API is a binary stable API to the Mojo system. There are
11 binary. The contents of this directory are not binary stable because each
16 C++ and JavaScript. Clients are expected to statically link with the generated
24 protocol, clients are expected to link dynamically against the standard GLES2
33 by which these messages are transported is not stable. To insulate themselves
34 from changes in the underlying transport, clients are expected to link against
41 clients are expected to ignore this directory.
/external/llvm/docs/CommandGuide/
Dllvm-diff.rst19 names of local values, are ignored.
25 are compared; otherwise, all global values are compared, and
26 diagnostics are produced for globals which only appear in one module
31 then the corresponding successors are compared; otherwise they are
53 attributes, are not diagnosed.
/external/openssh/
Dmoduli.012 numbers that are likely to be useful. A second primality testing pass,
14 are prime and are safe for use in Diffie-Hellman operations by sshd(8).
18 containing seven space-separated fields. These fields are as follows:
24 the prime modulus. Supported types are:
31 are Sophie Germain primes (type 4). Further primality
33 (type 2) that are ready for use in sshd(8). Other
34 types are not used by OpenSSH.
47 ssh-keygen(1) primality tests are Miller-Rabin tests
/external/llvm/test/CodeGen/Mips/
Deh-return32.ll15 ; check that $a0-$a3 are saved on stack.
21 ; check that .cfi_offset directives are emitted for $a0-$a3.
27 ; check that stack adjustment and handler are put in $v1 and $v0.
33 ; check that $a0-$a3 are restored from stack.
56 ; check that $a0-$a3 are saved on stack.
62 ; check that .cfi_offset directives are emitted for $a0-$a3.
68 ; check that stack adjustment and handler are put in $v1 and $v0.
72 ; check that $a0-$a3 are restored from stack.

12345678910>>...227