| /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 | 20 2 3 #text 0 1 WE need lot of garbage now to trigger the problem
25 2 3 #text 0 1 WE need lot of garbage now to trigger the problem
30 2 3 #text 0 1 WE need lot of garbage now to trigger the problem
35 2 3 #text 0 1 WE need lot of garbage now to trigger the problem
40 2 3 #text 0 1 WE need lot of garbage now to trigger the problem
45 2 3 #text 0 1 WE need lot of garbage now to trigger the problem
50 2 3 #text 0 1 WE need lot of garbage now to trigger the problem
55 2 3 #text 0 1 WE need lot of garbage now to trigger the problem
60 2 3 #text 0 1 WE need lot of garbage now to trigger the problem
65 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/perfetto/docs/design-docs/ |
| D | heapprofd-sampling.md | 15 probability p of being sampled. In theory we can think of each byte undergoing a
16 Bernoulli trial. The reason we use a random sampling approach, as opposed to
20 To scale the sampled bytes to the correct scale, we multiply by 1 / p, i.e. if
21 we sample a byte with probability 10%, then each byte sampled represents 10
29 1. We look at an allocation
32 chance of it being sampled at least once, we return the size of the
35 3. If the size of the allocation is smaller, then we compute the number of times
36 we would draw a sample if we sampled each byte with the given sampling rate:
38 * In practice we do this by keeping track of the arrival time of the next
39 sample. When an allocation happens, we subtract its size from the arrival
[all …]
|
| /external/libcups/ |
| D | config.h.in | 96 * Do we have domain socket support, and if so what is the default one?
131 * Do we have posix_spawn?
138 * Do we have ZLIB?
146 * Do we have PAM stuff?
156 * Do we have <shadow.h>?
163 * Do we have <crypt.h>?
186 * Do we have the long long type?
201 * Do we have the strtoll() function?
212 * Do we have the strXXX() functions?
221 * Do we have the geteuid() function?
[all …]
|
| /external/llvm-project/llvm/docs/HistoricalNotes/ |
| D | 2003-06-25-Reoptimizer1.txt | 6 We use opt to do Bytecode-to-bytecode instrumentation. Look at
14 exceeds a threshold, we identify a hot loop and perform second-level
16 target of the back-edge and the branch that causes the back-edge). We
23 We remove the first-level instrumentation by overwriting the CALL to
27 LLVM BasicBlock*s. We only keep track of paths that start at the
30 How do we keep track of which edges to instrument, and which edges are
41 3) Mark BBs which end in edges that exit the hot region; we need to
44 Assume that there is 1 free register. On SPARC we use %g1, which LLC
46 edge which corresponds to a conditional branch, we shift 0 for not
48 through the hot region. Silently fail if we need more than 64 bits.
[all …]
|
| /external/llvm/docs/HistoricalNotes/ |
| D | 2003-06-25-Reoptimizer1.txt | 6 We use opt to do Bytecode-to-bytecode instrumentation. Look at
14 exceeds a threshold, we identify a hot loop and perform second-level
16 target of the back-edge and the branch that causes the back-edge). We
23 We remove the first-level instrumentation by overwriting the CALL to
27 LLVM BasicBlock*s. We only keep track of paths that start at the
30 How do we keep track of which edges to instrument, and which edges are
41 3) Mark BBs which end in edges that exit the hot region; we need to
44 Assume that there is 1 free register. On SPARC we use %g1, which LLC
46 edge which corresponds to a conditional branch, we shift 0 for not
48 through the hot region. Silently fail if we need more than 64 bits.
[all …]
|
| /external/llvm/docs/tutorial/ |
| D | LangImpl09.rst | 12 LLVM <index.html>`_" tutorial. In chapters 1 through 8, we've built a
19 source that the programmer wrote. In LLVM we generally use a format
23 The short summary of this chapter is that we'll go through the
27 Caveat: For now we can't debug via the JIT, so we'll need to compile
29 we'll make a few modifications to the running of the language and
30 how programs are compiled. This means that we'll have a source file
32 interactive JIT. It does involve a limitation that we can only
36 Here's the sample program we'll be compiling:
54 locations more difficult. In LLVM IR we keep the original source location
61 tutorial we're going to avoid optimization (as you'll see with one of the
[all …]
|
| /external/libcups/xcode/ |
| D | config.h | 98 * Do we have domain socket support, and if so what is the default one?
133 * Do we have posix_spawn?
140 * Do we have ZLIB?
148 * Do we have PAM stuff?
160 * Do we have <shadow.h>?
167 * Do we have <crypt.h>?
190 * Do we have the long long type?
205 * Do we have the strtoll() function?
216 * Do we have the strXXX() functions?
225 * Do we have the geteuid() function?
[all …]
|
| /external/antlr/runtime/Cpp/include/ |
| D | antlr3collections.inl | 138 /* Now we need to allocate the root node. This makes it easier
139 * to use the tree as we don't have to do anything special
144 /* Now we seed the root node with the index being the
145 * highest left most bit we want to test, which limits the
151 /* And as we have nothing in here yet, we set both child pointers
159 * we use calloc() to initialise it.
172 /* the nodes are all gone now, so we need only free the memory
189 * then by definition (as the bit index decreases as we descent the trie)
190 * we have reached a 'backward' pointer. A backward pointer means we
192 * and it must either be the key we are looking for, or if not then it
[all …]
|
| /external/antlr/runtime/C/src/ |
| D | antlr3collections.c | 128 // All we have to do is create the hashtable tracking structure in antlr3HashTableNew()
212 /* Allow sparse tables, though we don't create them as such at present in antlr3HashFree()
222 /* Save next entry - we do not want to access memory in entry after we in antlr3HashFree()
236 /* Free the key memory - we know that we allocated this in antlr3HashFree()
246 entry = nextEntry; /* Load next pointer to see if we shoud free it */ in antlr3HashFree()
254 /* Now we can free the bucket memory in antlr3HashFree()
259 /* Now we free teh memory for the table itself in antlr3HashFree()
281 /* First we need to know the hash of the provided key in antlr3HashRemoveI()
285 /* Knowing the hash, we can find the bucket in antlr3HashRemoveI()
289 /* Now, we traverse the entries in the bucket until in antlr3HashRemoveI()
[all …]
|
| /external/libcups/vcnet/ |
| D | config.h | 32 * To avoid moronic problems like this, we #define the POSIX function
177 * Do we have domain socket support, and if so what is the default one?
212 * Do we have posix_spawn?
219 * Do we have ZLIB?
227 * Do we have PAM stuff?
237 * Do we have <shadow.h>?
244 * Do we have <crypt.h>?
267 * Do we have the long long type?
282 * Do we have the strtoll() function?
293 * Do we have the strXXX() functions?
[all …]
|
| /external/llvm-project/llvm/docs/tutorial/MyFirstLanguageFrontend/ |
| D | LangImpl09.rst | 12 LLVM <index.html>`_" tutorial. In chapters 1 through 8, we've built a
19 source that the programmer wrote. In LLVM we generally use a format
23 The short summary of this chapter is that we'll go through the
27 Caveat: For now we can't debug via the JIT, so we'll need to compile
29 we'll make a few modifications to the running of the language and
30 how programs are compiled. This means that we'll have a source file
32 interactive JIT. It does involve a limitation that we can only
36 Here's the sample program we'll be compiling:
54 locations more difficult. In LLVM IR we keep the original source location
61 tutorial we're going to avoid optimization (as you'll see with one of the
[all …]
|
| /external/ltp/testcases/kernel/controllers/freezer/ |
| D | 00_description.txt | 3 We initially try to freeze the cgroup but then try to cancel that.
4 After we cancel the sleep process should eventually reach the thawed
5 state. We expect the process to still be alive as we cleanup the test.
9 The sleep process is frozen. We then kill the sleep process.
10 Then we unfreeze the sleep process and see what happens. We expect the
16 The sleep process is frozen. We then move the sleep process to a THAWED
17 cgroup. We expect moving the sleep process to fail.
22 part of. We then thaw the subshell process. We expect the unthawed
28 The sleep process is frozen. We then wait until the sleep process should
29 have exited. Then we unfreeze the sleep process. We expect the
[all …]
|
| /external/llvm-project/llvm/docs/ |
| D | MergeFunctions.rst | 20 explains how we could combine equal functions correctly to keep the module
38 LLVM code fundamentals. In this article, we assume the reader is familiar with
44 We will use terms such as
85 Do we need to merge functions? The obvious answer is: Yes, that is quite a
86 possible case. We usually *do* have duplicates and it would be good to get rid
87 of them. But how do we detect duplicates? This is the idea: we split functions
89 we compare the "bricks" themselves, and then do our conclusions about functions
93 (let's assume we have only one address space), one function stores a 64-bit
95 mentioned above, and if functions are identical, except the parameter type (we
96 could consider it as a part of function type), then we can treat a ``uint64_t``
[all …]
|
| /external/webrtc/tools_webrtc/mb/docs/ |
| D | design_spec.md | 10 1. "bot toggling" - make it so that we can easily flip a given bot
18 we need to wrap both the `gyp_chromium` invocation to generate the
81 We start with the following requirements and observations:
83 * In an ideal (un-resource-constrained) world, we would build and test
85 necessarily mean that we would build 'all' on every patch (see below).
87 * In the real world, however, we do not have an infinite number of machines,
88 and try jobs are not infinitely fast, so we need to balance the desire
90 times, given the number of machines we have.
92 * Also, since we run most try jobs against tip-of-tree Chromium, by
98 affected for unrelated reasons. We want to rebuild and test only the
[all …]
|
| /external/libchrome/base/message_loop/ |
| D | message_pump_glib.cc | 28 // Be careful here. TimeDelta has a precision of microseconds, but we want a in GetTimeIntervalMilliseconds()
34 // If this value is negative, then we need to run delayed work soon. in GetTimeIntervalMilliseconds()
50 // making Check a second chance to tell GLib we are ready for Dispatch.
74 // Thus it is important to only return true from prepare or check if we
75 // actually have events or work to do. We also need to make sure we keep
80 // For the GLib pump we try to follow the Windows UI pump model:
81 // - Whenever we receive a wakeup event or the timer for delayed work expires,
82 // we run DoWork and/or DoDelayedWork. That part will also run in the other
84 // - We also run DoWork, DoDelayedWork, and possibly DoIdleWork in the main
94 // We always return FALSE, so that our timeout is honored. If we were in WorkSourcePrepare()
[all …]
|
| /external/llvm-project/lldb/test/API/python_api/frame/get-variables/ |
| D | TestGetVariables.py | 42 len(copy_names), 0, "%s: we didn't find variables: %s in value list (%s)" %
107 # Verify if we ask for only arguments that we got what we expect
113 "There should be %i arguments, but we are reporting %i" %
122 # Verify if we ask for only locals that we got what we expect
128 "There should be %i local variables, but we are reporting %i" %
133 # Verify if we ask for only statics that we got what we expect
140 "There should be %i static variables, but we are reporting %i" %
146 # Verify if we ask for arguments and locals that we got what we expect
155 "There should be %i %s (%s) but we are reporting %i (%s)" %
163 # Verify if we ask for arguments and statics that we got what we expect
[all …]
|
| /external/llvm/docs/ |
| D | MergeFunctions.rst | 22 explains how we could combine equal functions correctly, keeping module valid.
31 cover only common cases, and thus avoid cases when after minor code changes we
39 code fundamentals. In this article we suppose reader is familiar with
45 We will use such terms as
77 again and again, and yet you don't understand why we implemented it that way.
79 We hope that after this article reader could easily debug and improve
98 Do we need to merge functions? Obvious thing is: yes that's a quite possible
99 case, since usually we *do* have duplicates. And it would be good to get rid of
100 them. But how to detect such a duplicates? The idea is next: we split functions
101 onto small bricks (parts), then we compare "bricks" amount, and if it equal,
[all …]
|
| /external/libxkbcommon/doc/ |
| D | quick-guide.md | 6 the library. We will employ a few use-cases to lead the examples:
32 Before we can do anything interesting, we need a library context:
46 Next we need to create a keymap, `xkb_keymap`. This is an immutable object
50 If we are an evdev client, we have nothing to go by, so we need to ask
54 by the X server. With it, we can fill a struct called `xkb_rule_names`;
73 If we are a Wayland client, the compositor gives us a string complete
74 with a keymap. In this case, we can create the keymap object like this:
87 If we are an X11 client, we are better off getting the keymap from the
88 X server directly. For this we need to choose the XInput device; here
89 we will use the core keyboard device:
[all …]
|
| /external/llvm-project/llvm/lib/Target/WebAssembly/ |
| D | WebAssemblyExceptionInfo.cpp | 54 auto WE = std::make_unique<WebAssemblyException>(EHPad); in recalculate() local
55 discoverAndMapException(WE.get(), MDT, MDF); in recalculate()
56 Exceptions.push_back(std::move(WE)); in recalculate()
62 WebAssemblyException *WE = getExceptionFor(MBB); in recalculate() local
63 for (; WE; WE = WE->getParentException()) in recalculate()
64 WE->addBlock(MBB); in recalculate()
71 for (auto &WE : Exceptions) { in recalculate() local
72 ExceptionPointers.push_back(WE.get()); in recalculate()
73 if (WE->getParentException()) in recalculate()
74 WE->getParentException()->getSubExceptions().push_back(std::move(WE)); in recalculate()
[all …]
|