Searched refs:enters (Results 1 – 25 of 75) sorted by relevance
123
| /external/clang/test/SemaObjC/ |
| D | arc-jump-block.m | 22 …c((&_dispatch_main_q), ^{ [self pageLeft]; }); // expected-note 3 {{jump enters lifetime of block …
25 …((&_dispatch_main_q), ^{ [self pageRight]; }); // expected-note 2 {{jump enters lifetime of block …
87 int test2(id obj, int state) { // expected-note {{jump enters lifetime of block}} FIXME: weird loca…
|
| /external/autotest/server/site_tests/firmware_CorruptBothFwSigAB/ |
| D | control.dev | 22 fails and enters recovery mode. This test then checks the success of the
|
| D | control | 22 fails and enters recovery mode. This test then checks the success of the
|
| /external/autotest/server/site_tests/firmware_Cr50DeviceState/ |
| D | control | 21 any interrupt storms and that Cr50 enters regular or deep sleep reasonable
|
| /external/e2fsprogs/doc/RelNotes/ |
| D | v1.29.txt | 18 If the bone-headed user enters the root filesystem twice in
|
| D | v1.41.13 | 107 user enters a typo'ed device name, instead of blathering on about
|
| /external/autotest/server/site_tests/firmware_CorruptBothKernelAB/ |
| D | control.dev | 24 and enters recovery mode. This test then checks the success of the
|
| D | control | 24 and enters recovery mode. This test then checks the success of the
|
| /external/autotest/server/site_tests/firmware_CorruptBothFwBodyAB/ |
| D | control.dev | 25 the firmware verification fails on loading RW firmware and enters recovery
|
| D | control | 25 the firmware verification fails on loading RW firmware and enters recovery
|
| /external/ltp/testcases/kernel/controllers/ |
| D | README | 63 cpu controller. If yes it enters lower directory and compiles the source files
|
| /external/ltp/doc/ |
| D | namespaces-helper-tools.txt | 20 ** enters the namespace(s) of a process specified by a PID
|
| /external/u-boot/arch/arm/mach-rockchip/ |
| D | Kconfig | 213 re-enters at the same address/to the same code as previously.
227 re-enters at the same address/to the same code as previously.
|
| /external/python/cpython3/Doc/reference/ |
| D | toplevel_components.rst | 58 or standard input is a tty device, the interpreter enters interactive mode;
|
| /external/mesa3d/src/gallium/state_trackers/xa/ |
| D | README | 67 As soon as the library enters a mesa release branch, if not earlier, major
|
| /external/python/cpython2/Doc/reference/ |
| D | toplevel_components.rst | 57 or standard input is a tty device, the interpreter enters interactive mode;
|
| /external/strace/ |
| D | README-linux-ptrace | 93 When running tracee enters ptrace-stop, it notifies its tracer using
136 thread is traced, it enters signal-delivery-stop. By this point, signal
229 notifications (except SIGKILL death) to tracer, even if tracer enters
281 If tracee was restarted by PTRACE_SYSCALL, tracee enters
283 restarts it with PTRACE_SYSCALL, tracee enters syscall-exit-stop when
|
| /external/deqp/external/openglcts/ |
| D | CONTRIBUTING.md | 30 1. `init()` - called when executor enters test node
|
| /external/iproute2/doc/actions/ |
| D | ifb-README | 35 all however is dependent on whatever rules the admin enters.
|
| /external/grpc-grpc/src/objective-c/ |
| D | NetworkTransitionBehavior.md | 13 disconnected and enters TRANSIENT\_FAILURE state.
|
| /external/openssh/ |
| D | OVERVIEW | 146 operations, and finally the server enters the normal session
|
| /external/iputils/doc/ |
| D | rdisc.sgml | 77 Normally <command/rdisc/ only accepts (and enters in the kernel routing
|
| /external/python/cpython2/Doc/library/ |
| D | code.rst | 164 newline. When the user enters the EOF key sequence, :exc:`EOFError` is raised.
|
| /external/python/cpython3/Doc/library/ |
| D | code.rst | 182 newline. When the user enters the EOF key sequence, :exc:`EOFError` is raised.
|
| /external/python/cpython3/Lib/email/ |
| D | architecture.rst | 94 A header enters the model in one of two ways: via a Parser, or by being set to
|
123