Home
last modified time | relevance | path

Searched refs:We (Results 1 – 25 of 6304) sorted by relevance

12345678910>>...253

/external/ltp/testcases/kernel/controllers/freezer/
D00_description.txt3 We initially try to freeze the cgroup but then try to cancel that.
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
36 The sleep process is frozen. We then thaw the process before it exits.
[all …]
/external/llvm-project/llvm/utils/valgrind/
Dx86_64-pc-linux-gnu.supp30 We don't care if as leaks
36 We don't care if bash leaks
44 We don't care of cmp
50 We don't care if grep leaks
56 We don't care if python leaks
63 We don't care if sed leaks
71 We don't care about anything ld.so does.
Di386-pc-linux-gnu.supp31 We don't care if as leaks
37 We don't care if python leaks
44 We don't care about anything ld.so does.
/external/llvm/utils/valgrind/
Dx86_64-pc-linux-gnu.supp30 We don't care if as leaks
36 We don't care if bash leaks
44 We don't care of cmp
50 We don't care if grep leaks
56 We don't care if python leaks
63 We don't care if sed leaks
71 We don't care about anything ld.so does.
Di386-pc-linux-gnu.supp31 We don't care if as leaks
37 We don't care if python leaks
44 We don't care about anything ld.so does.
/external/llvm-project/llvm/docs/HistoricalNotes/
D2003-06-25-Reoptimizer1.txt6 We use opt to do Bytecode-to-bytecode instrumentation. Look at
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
51 and the return address of the countPath call. We keep track of the
52 number of iterations and the number of paths. We only run this
57 we have more than 5 we take the ones that are executed the most. We
71 We turn off llvm_first_trigger() calls with NOPs, but this would hide
75 We have a SIGALRM timer that counts time for us. Every time we get a
94 We copy the code from the original to the instrumentation version
[all …]
/external/llvm/docs/HistoricalNotes/
D2003-06-25-Reoptimizer1.txt6 We use opt to do Bytecode-to-bytecode instrumentation. Look at
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
51 and the return address of the countPath call. We keep track of the
52 number of iterations and the number of paths. We only run this
57 we have more than 5 we take the ones that are executed the most. We
71 We turn off llvm_first_trigger() calls with NOPs, but this would hide
75 We have a SIGALRM timer that counts time for us. Every time we get a
94 We copy the code from the original to the instrumentation version
[all …]
/external/swiftshader/third_party/llvm-10.0/llvm/lib/Target/SystemZ/
DREADME.txt5 The initial backend is deliberately restricted to z10. We should add support
35 We don't use the BRANCH ON INDEX instructions.
39 We only use MVC, XC and CLC for constant-length block operations.
40 We could extend them to variable-length operations too,
47 We don't use CUSE or the TRANSLATE family of instructions for string
52 We don't take full advantage of builtins like fabsl because the calling
66 We don't use ICM, STCM, or CLM.
70 We don't use ADD (LOGICAL) HIGH, SUBTRACT (LOGICAL) HIGH,
151 We might want to model all access registers and use them to spill
156 We might want to use the 'overflow' condition of eg. AR to support
/external/llvm-project/llvm/lib/Target/SystemZ/
DREADME.txt5 The initial backend is deliberately restricted to z10. We should add support
35 We don't use the BRANCH ON INDEX instructions.
39 We only use MVC, XC and CLC for constant-length block operations.
40 We could extend them to variable-length operations too,
47 We don't use CUSE or the TRANSLATE family of instructions for string
52 We don't take full advantage of builtins like fabsl because the calling
66 We don't use ICM, STCM, or CLM.
70 We don't use ADD (LOGICAL) HIGH, SUBTRACT (LOGICAL) HIGH,
151 We might want to model all access registers and use them to spill
156 We might want to use the 'overflow' condition of eg. AR to support
/external/llvm/lib/Target/SystemZ/
DREADME.txt5 The initial backend is deliberately restricted to z10. We should add support
35 We don't use the BRANCH ON INDEX instructions.
39 We only use MVC, XC and CLC for constant-length block operations.
40 We could extend them to variable-length operations too,
47 We don't use CUSE or the TRANSLATE family of instructions for string
52 We don't take full advantage of builtins like fabsl because the calling
66 We don't use ICM or STCM.
146 We might want to model all access registers and use them to spill
151 We might want to use the 'overflow' condition of eg. AR to support
/external/rust/crates/nix/
DCONVENTIONS.md14 We follow the conventions laid out in [Keep A CHANGELOG][kacl].
20 We do not define integer constants ourselves, but use or reexport them from the
23 We use the functions exported from [libc][libc] instead of writing our own
26 We use the `struct` definitions from [libc][libc] internally instead of writing
43 bitwise operations. We represent the types of these parameters by types defined
48 We name the type for a set of constants whose element's names start with `FOO_`
71 We represent sets of constants that are intended as mutually exclusive arguments
/external/llvm-project/llvm/test/tools/llvm-exegesis/Mips/
Dlit.local.cfg5 # We need support for Mips.
9 # We need to be running on an Mips host.
13 # We need libpfm to be installed and allow reading perf counters. We can
/external/llvm/test/CodeGen/X86/
Dtest-nofold.ll4 ; We want:
11 ; We don't want:
20 ; We also don't want:
27 ; We also don't want:
/external/llvm-project/llvm/test/tools/llvm-exegesis/AArch64/
Dlit.local.cfg5 # We need support for AArch64.
9 # We need to be running on an AArch64 host.
13 # We need libpfm to be installed and allow reading perf counters. We can
/external/llvm-project/llvm/test/CodeGen/X86/
Dtest-nofold.ll4 ; We want:
11 ; We don't want:
20 ; We also don't want:
27 ; We also don't want:
/external/angle/doc/
DUpdate20120704.md3 We haven't posted an update on the development status of ANGLE in quite some
17 We have recently completed the implementation of depth texture support
28 We have also made a number of improvements in the shader compiler.
30 * We addressed a number of defects related to scoping differences between HLSL and
31 GLSL and improved the scoping support in ANGLE's compiler front-end. We also
34 * We addressed a number of correctness issues in the GLSL to HLSL
35 translation process. We fixed some bugs related to constant propagation and
41 * We implemented detection
63 explicitly defined. We use these new functions instead of the original ones in
71 current ES 2.0 implementations.  We would only be able to achieve parity with
[all …]
/external/llvm-project/llvm/test/tools/llvm-exegesis/X86/
Dlit.local.cfg5 # We need support for X86.
9 # We need to be running on an X86 host.
13 # We need libpfm to be installed and allow reading perf counters. We can
/external/llvm-project/llvm/test/Transforms/Inline/
Dinline-no-builtin-compatible.ll21 ; We can inline a function that allows all builtins into one with a single
33 ; We can inline a function that allows all builtins into one with all
45 ; We can inline a function with a single nobuiltin into one with all nobuiltins.
56 ; We can't inline a function with any given nobuiltin into one that allows all
68 ; We can't inline a function with all nobuiltins into one that allows all
80 ; We can't inline a function with a specific nobuiltin into one with a
/external/okio/docs/
Dcode_of_conduct.md5 of releasing and managing open source software. We’ve seen incredible support and enthusiasm from
10 unacceptable behavior. We are committed to providing a welcoming and inspiring community for all and
15 * **Be open**: We invite anyone to participate in any aspect of our projects. Our community is
23 * **Be respectful**: We expect people to work together to resolve conflict, assume good intentions,
26 * **Be collaborative**: Collaboration reduces redundancy and improves the quality of our work. We
39 collaborative, shared environment, and goals. We expect it to be followed in spirit as much as in
45 We encourage everyone to participate and are committed to building a community for all. Although we
54 religion, sexual orientation, socioeconomic status, and technical ability. We will not tolerate
70 We are thankful for their work.
/external/curl/tests/data/
Dtest109715 HTTP/1.1 200 We are fine and cool
24 HTTP/1.1 200 We are fine and cool
30 HTTP/1.1 200 We are fine and cool
33 HTTP/1.1 200 We are fine and cool
/external/vixl/
D.clang-tidy2 # We use the clang-tidy defaults and the Google styles as a baseline, with a
11 # We don't put names on TODOs.
16 # We do this in internal contexts (typically in .cc files), but clang-tidy
19 # We follow this rule, but have some exceptions that are annotated using
/external/zlib/
DAndroid.bp35 // We need a non-NEON libz.a for the NDK, and cpu_features.c won't build
42 // We no longer support non-Neon platform builds, but the NDK just has one libz.
61 // We should have a conversation about that, but not until we at least have
107 // We do support hidden visibility, so turn that on.
109 // We do support const, so turn that on.
203 // We do support hidden visibility, so turn that on.
205 // We do support const, so turn that on.
235 // We build zlib_bench32 and zlib_bench64 so it's easy to test LP32.
/external/llvm/test/CodeGen/Mips/
Dabiflags32.ll6 ; We don't emit '.module fp=32' for compatibility with binutils 2.24 which
11 ; We do emit '.module fp=64' though since it contradicts the default value.
15 ; We don't emit '.module fp=64' for compatibility with binutils 2.24 which
/external/llvm-project/llvm/test/tools/llvm-exegesis/X86/lbr/
Dlit.local.cfg5 # We need support for X86.
9 # We need to be running on an X86 host.
13 # We need libpfm to be installed and the host to be support LBR format with cycles.
/external/skia/fuzz/
DREADME.md1 We fuzz Skia using oss-fuzz, which in turn uses fuzzing engines such as libfuzzer, afl-fuzz,
4 We define a `fuzzer` to be a targeted bit of code that takes a randomized input and executes code
6 file and attempts to turn it into an `SkImage`. We also have a canvas fuzzer which takes in a random

12345678910>>...253