| /external/libxml2/result/ |
| D | ent9 | 7 <p> WE need lot of garbage now to trigger the problem</p>
8 <p> WE need lot of garbage now to trigger the problem</p>
9 <p> WE need lot of garbage now to trigger the problem</p>
10 <p> WE need lot of garbage now to trigger the problem</p>
11 <p> WE need lot of garbage now to trigger the problem</p>
12 <p> WE need lot of garbage now to trigger the problem</p>
13 <p> WE need lot of garbage now to trigger the problem</p>
14 <p> WE need lot of garbage now to trigger the problem</p>
15 <p> WE need lot of garbage now to trigger the problem</p>
16 <p> WE need lot of garbage now to trigger the problem</p>
[all …]
|
| D | ent9.rdr | 11 2 3 #text 0 1 WE need lot of garbage now to trigger the problem
16 2 3 #text 0 1 WE need lot of garbage now to trigger the problem
21 2 3 #text 0 1 WE need lot of garbage now to trigger the problem
26 2 3 #text 0 1 WE need lot of garbage now to trigger the problem
31 2 3 #text 0 1 WE need lot of garbage now to trigger the problem
36 2 3 #text 0 1 WE need lot of garbage now to trigger the problem
41 2 3 #text 0 1 WE need lot of garbage now to trigger the problem
46 2 3 #text 0 1 WE need lot of garbage now to trigger the problem
51 2 3 #text 0 1 WE need lot of garbage now to trigger the problem
56 2 3 #text 0 1 WE need lot of garbage now to trigger the problem
[all …]
|
| D | ent9.rde | 21 2 3 #text 0 1 WE need lot of garbage now to trigger the problem
26 2 3 #text 0 1 WE need lot of garbage now to trigger the problem
31 2 3 #text 0 1 WE need lot of garbage now to trigger the problem
36 2 3 #text 0 1 WE need lot of garbage now to trigger the problem
41 2 3 #text 0 1 WE need lot of garbage now to trigger the problem
46 2 3 #text 0 1 WE need lot of garbage now to trigger the problem
51 2 3 #text 0 1 WE need lot of garbage now to trigger the problem
56 2 3 #text 0 1 WE need lot of garbage now to trigger the problem
61 2 3 #text 0 1 WE need lot of garbage now to trigger the problem
66 2 3 #text 0 1 WE need lot of garbage now to trigger the problem
[all …]
|
| D | ent9.sax | 28 SAX.characters( WE need lot of garbage now to, 50)
33 SAX.characters( WE need lot of garbage now to, 50)
38 SAX.characters( WE need lot of garbage now to, 50)
43 SAX.characters( WE need lot of garbage now to, 50)
48 SAX.characters( WE need lot of garbage now to, 50)
53 SAX.characters( WE need lot of garbage now to, 50)
58 SAX.characters( WE need lot of garbage now to, 50)
63 SAX.characters( WE need lot of garbage now to, 50)
68 SAX.characters( WE need lot of garbage now to, 50)
73 SAX.characters( WE need lot of garbage now to, 50)
[all …]
|
| D | ent9.sax2 | 28 SAX.characters( WE need lot of garbage now to, 50)
33 SAX.characters( WE need lot of garbage now to, 50)
38 SAX.characters( WE need lot of garbage now to, 50)
43 SAX.characters( WE need lot of garbage now to, 50)
48 SAX.characters( WE need lot of garbage now to, 50)
53 SAX.characters( WE need lot of garbage now to, 50)
58 SAX.characters( WE need lot of garbage now to, 50)
63 SAX.characters( WE need lot of garbage now to, 50)
68 SAX.characters( WE need lot of garbage now to, 50)
73 SAX.characters( WE need lot of garbage now to, 50)
[all …]
|
| /external/libxml2/test/ |
| D | ent9 | 6 <p> WE need lot of garbage now to trigger the problem</p>
7 <p> WE need lot of garbage now to trigger the problem</p>
8 <p> WE need lot of garbage now to trigger the problem</p>
9 <p> WE need lot of garbage now to trigger the problem</p>
10 <p> WE need lot of garbage now to trigger the problem</p>
11 <p> WE need lot of garbage now to trigger the problem</p>
12 <p> WE need lot of garbage now to trigger the problem</p>
13 <p> WE need lot of garbage now to trigger the problem</p>
14 <p> WE need lot of garbage now to trigger the problem</p>
15 <p> WE need lot of garbage now to trigger the problem</p>
[all …]
|
| /external/libxml2/result/noent/ |
| D | ent9 | 7 <p> WE need lot of garbage now to trigger the problem</p>
8 <p> WE need lot of garbage now to trigger the problem</p>
9 <p> WE need lot of garbage now to trigger the problem</p>
10 <p> WE need lot of garbage now to trigger the problem</p>
11 <p> WE need lot of garbage now to trigger the problem</p>
12 <p> WE need lot of garbage now to trigger the problem</p>
13 <p> WE need lot of garbage now to trigger the problem</p>
14 <p> WE need lot of garbage now to trigger the problem</p>
15 <p> WE need lot of garbage now to trigger the problem</p>
16 <p> WE need lot of garbage now to trigger the problem</p>
[all …]
|
| /external/pcre/dist/testdata/ |
| D | testoutput18-16 | 97 No need char
109 Need char = \x{dc00}
121 No need char
133 No need char
145 Need char = \x{dc00}
157 Need char = \x{dc00}
169 Need char = \x{dfff}
181 No need char
193 No need char
205 No need char
[all …]
|
| D | testoutput18-32 | 95 No need char
107 No need char
119 No need char
131 No need char
143 No need char
155 No need char
167 No need char
179 No need char
191 No need char
203 No need char
[all …]
|
| D | testoutput2 | 18 No need char
24 Need char = 'c'
42 No need char
58 Need char = 'c'
64 Need char = 'c'
70 Need char = 'c'
76 No need char
82 No need char
157 Need char = 'b'
163 Need char = 'b'
[all …]
|
| D | testoutput15 | 87 Need char = 'x'
263 Need char = \x{80}
275 Need char = \x{80}
287 Need char = \x{80}
299 Need char = \x{80}
311 Need char = \x{bf}
323 Need char = \x{bf}
335 Need char = \x{80}
347 Need char = \x{80}
359 Need char = \x{bf}
[all …]
|
| /external/gmock/ |
| D | README | 50 framework of your choice; although it will still need Google Test as
80 We welcome patches. If you plan to contribute a patch, you need to
127 system to build Google Mock (described below), you'll need to
138 Note that you should only need to complete this step once. The
140 of the build system that need to be changed.
143 will fail. You may need to explicitly specify a version to use. For
154 To build Google Mock and your tests that use it, you need to tell your
190 (We need -pthread as Google Test and Google Mock use threads.)
252 subset of TR1 tuple that's enough for Google Mock's need. Google Mock
256 Usually you don't need to care about which tuple library Google Test
[all …]
|
| /external/harfbuzz_ng/docs/ |
| D | usermanual-what-is-harfbuzz.xml | 8 <section id="why-do-i-need-it">
9 <title>Why do I need it?</title>
16 you will probably not need to use Harfbuzz - normally higher level
21 or graphics library yourself, you will need to perform text
23 reasons why you need it:
32 the font in order to display it, you need to consult a table
72 that you need to render.
77 Other languages have marks and accents which need to be
89 precomposed glyph within your font or if you need to compose a
96 If this is something that you need to do, then you need a text
|
| /external/google-breakpad/src/testing/ |
| D | README | 50 framework of your choice; although it will still need Google Test as
80 We welcome patches. If you plan to contribute a patch, you need to
127 system to build Google Mock (described below), you'll need to
138 Note that you should only need to complete this step once. The
140 of the build system that need to be changed.
143 will fail. You may need to explicitly specify a version to use. For
154 To build Google Mock and your tests that use it, you need to tell your
244 subset of TR1 tuple that's enough for Google Mock's need. Google Mock
248 Usually you don't need to care about which tuple library Google Test
250 you need to tell Google Test and Google Mock to use the same TR1 tuple
[all …]
|
| /external/gtest/ |
| D | README | 56 Also, you'll need CMake 2.6.4 or higher if you want to build the
62 We welcome patches. If you plan to contribute a patch, you need to
109 To build Google Test and your tests that use it, you need to tell your
130 (We need -pthread as Google Test uses threads.)
195 If you still need to use the legacy build scripts, here's how:
222 above, you need to either:
249 enough for its own need, and will automatically use this when the
252 Usually you don't need to care about which tuple library Google Test
253 uses. However, if your project already uses TR1 tuple, you need to
289 When Google Test uses pthread, you may need to add flags to your
[all …]
|
| /external/libvpx/libvpx/third_party/googletest/src/ |
| D | README | 56 Also, you'll need CMake 2.6.4 or higher if you want to build the
62 We welcome patches. If you plan to contribute a patch, you need to
109 To build Google Test and your tests that use it, you need to tell your
130 (We need -pthread as Google Test uses threads.)
195 If you still need to use the legacy build scripts, here's how:
222 above, you need to either:
249 enough for its own need, and will automatically use this when the
252 Usually you don't need to care about which tuple library Google Test
253 uses. However, if your project already uses TR1 tuple, you need to
289 When Google Test uses pthread, you may need to add flags to your
[all …]
|
| /external/vulkan-validation-layers/tests/gtest-1.7.0/ |
| D | README | 56 Also, you'll need CMake 2.6.4 or higher if you want to build the
62 We welcome patches. If you plan to contribute a patch, you need to
109 To build Google Test and your tests that use it, you need to tell your
130 (We need -pthread as Google Test uses threads.)
195 If you still need to use the legacy build scripts, here's how:
222 above, you need to either:
249 enough for its own need, and will automatically use this when the
252 Usually you don't need to care about which tuple library Google Test
253 uses. However, if your project already uses TR1 tuple, you need to
289 When Google Test uses pthread, you may need to add flags to your
[all …]
|
| /external/antlr/antlr-3.4/ |
| D | antlrjar.xml | 5 all of the classes we need to run an executable jar in standalone
17 The only output format we need is the executable jar file
32 dependencies, so we only need to name the Tool module
46 above modules need, which do we want and which do we not.
54 Exclude the antlr-master pom from the jar - we don't need it
61 uber jar that can run with java -jar and need not have
82 We need the output classes and resources etc.
|
| D | antlrsources.xml | 42 <!-- We need to described the source code of each of the modules we want
68 directory, we need to map the output directory so that
83 <!-- In the base runtime/Java directory, we need to include a number
86 so they need to be named here (which nicely documents what
114 directory, we need to map the output directory so that
131 <!-- In the base tool directory, we need to include a number
134 so they need to be named here (which nicely documents what
158 we need to describe them in their own fileset. No output mapping is required here
|
| /external/google-breakpad/src/testing/gtest/ |
| D | README | 56 Also, you'll need CMake 2.6.4 or higher if you want to build the
62 We welcome patches. If you plan to contribute a patch, you need to
109 To build Google Test and your tests that use it, you need to tell your
194 If you still need to use the legacy build scripts, here's how:
221 above, you need to either:
248 enough for its own need, and will automatically use this when the
251 Usually you don't need to care about which tuple library Google Test
252 uses. However, if your project already uses TR1 tuple, you need to
288 When Google Test uses pthread, you may need to add flags to your
292 script, you'll need to read your compiler and linker's manual to
[all …]
|
| /external/freetype/src/gzip/ |
| D | inflate.c | 40 uLong need; /* stream check value */ member
196 z->state->sub.check.need = (uLong)NEXTBYTE << 24; in inflate()
200 z->state->sub.check.need += (uLong)NEXTBYTE << 16; in inflate()
204 z->state->sub.check.need += (uLong)NEXTBYTE << 8; in inflate()
208 z->state->sub.check.need += (uLong)NEXTBYTE; in inflate()
209 z->adler = z->state->sub.check.need; in inflate()
214 z->msg = (char*)"need dictionary"; in inflate()
239 z->state->sub.check.need = (uLong)NEXTBYTE << 24; in inflate()
243 z->state->sub.check.need += (uLong)NEXTBYTE << 16; in inflate()
247 z->state->sub.check.need += (uLong)NEXTBYTE << 8; in inflate()
[all …]
|
| /external/protobuf/gtest/ |
| D | README | 56 Also, you'll need CMake 2.6.4 or higher if you want to build the
62 We welcome patches. If you plan to contribute a patch, you need to
109 To build Google Test and your tests that use it, you need to tell your
194 If you still need to use the legacy build scripts, here's how:
238 enough for its own need, and will automatically use this when the
241 Usually you don't need to care about which tuple library Google Test
242 uses. However, if your project already uses TR1 tuple, you need to
278 When Google Test uses pthread, you may need to add flags to your
282 script, you'll need to read your compiler and linker's manual to
295 to the compiler flags. You'll also need to tell the linker to produce
[all …]
|
| /external/proguard/src/proguard/classfile/attribute/annotation/ |
| D | TypeAnnotation.java | 69 // We don't need double dispatching here, since there is only one in targetInfoAccept()
80 // We don't need double dispatching here, since there is only one in targetInfoAccept()
91 // We don't need double dispatching here, since there is only one in targetInfoAccept()
102 // We don't need double dispatching here, since there is only one in targetInfoAccept()
115 // We don't need double dispatching here, since there is only one in typePathInfosAccept()
129 // We don't need double dispatching here, since there is only one in typePathInfosAccept()
143 // We don't need double dispatching here, since there is only one in typePathInfosAccept()
157 // We don't need double dispatching here, since there is only one in typePathInfosAccept()
|
| /external/antlr/antlr-3.4/runtime/C/src/ |
| D | antlr3rewritestreams.c | 62 // so we can reuse it if we need to.
68 // need to clear any vector it has. This is so any in freeRS()
113 // need to clear any vector it has. This is so any in freeNodeRS()
209 // Ok, we need to allocate a new one as there were none on the stack. in antlr3RewriteRuleElementStreamNewAE()
210 // First job is to create the memory we need. in antlr3RewriteRuleElementStreamNewAE()
261 // First job is to create the memory we need. in antlr3RewriteRuleElementStreamNewAEE()
270 // Stream seems good so we need to add the supplied element in antlr3RewriteRuleElementStreamNewAEE()
284 // First job is to create the memory we need. in antlr3RewriteRuleElementStreamNewAEV()
293 // Stream seems good so we need to install the vector we were in antlr3RewriteRuleElementStreamNewAEV()
313 // First job is to create the memory we need. in antlr3RewriteRuleTOKENStreamNewAE()
[all …]
|
| /external/antlr/antlr-3.4/runtime/Delphi/ |
| D | README.TXT | 18 You need to use Delphi 2009 or a later version to be able to use this target.
23 To use the Delphi target, you only need to put the runtime source code in a
35 In your projects, you usually only need to use the Antlr.Runtime unit, and the
62 Here is a short list of Delphi specific issues you need to take into account
137 the parser/lexer unit. This means that you need to specify the full name of
148 inside the rule, makes use of a local variable, then you need to declare that
168 If you need to add units to the uses clause of the generated units, then you can
171 then you will need to use the Classes unit.
172 Use the @usesInterface action if you need the units to appear in the interface
173 part, or @usesImplementation if you only need a unit inside the implementation.
[all …]
|