| /hardware/qcom/display/msm8994/libhwcomposer/ |
| hwc_utils.cpp | [all...] |
| /bionic/tests/ |
| dlext_test.cpp | 578 // close the 'wrong' ends of the pipes in the child
604 // close the 'wrong' ends of the pipes in the parent
626 // Close pipes and wait for children to exit
[all...] |
| /external/mesa3d/src/amd/addrlib/r800/ |
| siaddrlib.cpp | 99 * Get number pipes
101 * num pipes
117 numPipes = m_pipes; // Suppose we should still have a global pipes
[all...] |
| /external/python/cpython2/Doc/faq/ |
| library.rst | 514 How do I run a subprocess with pipes connected to both input and output?
583 Note that many interactive programs (e.g. vi) don't work well with pipes
585 ("ptys") instead of pipes. Or you can use a Python interface to Don Libes'
[all...] |
| /external/v8/tools/mb/ |
| mb.py | 20 import pipes
[all...] |
| /external/python/cpython2/Doc/library/ |
| multiprocessing.rst | 113 **Pipes**
499 Pipes and Queues
[all...] |
| /external/google-breakpad/src/testing/gtest/src/ |
| gtest-death-test.cc | 585 // implementation uses pipes for child-to-parent communication. But due to
586 // the specifics of pipes on Windows, some extra steps are required:
[all...] |
| /external/googletest/googletest/src/ |
| gtest-death-test.cc | 598 // implementation uses pipes for child-to-parent communication. But due to
599 // the specifics of pipes on Windows, some extra steps are required:
[all...] |
| /external/libmojo/mojo/edk/system/ |
| node_controller.cc | 461 // Relying on message pipes to be closed is not enough because the parent
628 // pipes.
[all...] |
| /external/libvpx/libvpx/third_party/googletest/src/src/ |
| gtest-death-test.cc | 598 // implementation uses pipes for child-to-parent communication. But due to
599 // the specifics of pipes on Windows, some extra steps are required:
[all...] |
| /external/llvm/utils/unittest/googletest/src/ |
| gtest-death-test.cc | 549 // implementation uses pipes for child-to-parent communication. But due to
550 // the specifics of pipes on Windows, some extra steps are required:
[all...] |
| /external/mesa3d/src/gallium/drivers/r300/ |
| r300_emit.c | 682 * only two pipes, and the second pipe's enable is on bit 3, not bit 1,
710 " pixel pipes!\n", gb_pipes);
[all...] |
| /external/mesa3d/src/gtest/src/ |
| gtest-death-test.cc | 587 // implementation uses pipes for child-to-parent communication. But due to
588 // the specifics of pipes on Windows, some extra steps are required:
[all...] |
| /external/one-true-awk/ |
| FIXES | 323 fflush() or fflush("") flushes all files and pipes.
472 pipes (thanks to Steve Adams for this helpful suggestion).
[all...] |
| /external/protobuf/gtest/src/ |
| gtest-death-test.cc | 499 // implementation uses pipes for child-to-parent communication. But due to
500 // the specifics of pipes on Windows, some extra steps are required:
[all...] |
| /external/python/cpython3/Doc/library/ |
| asyncio-eventloop.rst | 628 Connect pipes
632 Use :class:`ProactorEventLoop` to support pipes on Windows.
[all...] |
| /external/swiftshader/third_party/LLVM/utils/unittest/googletest/ |
| gtest-death-test.cc | 547 // implementation uses pipes for child-to-parent communication. But due to
548 // the specifics of pipes on Windows, some extra steps are required:
[all...] |
| /external/v8/testing/gtest/src/ |
| gtest-death-test.cc | 596 // implementation uses pipes for child-to-parent communication. But due to
597 // the specifics of pipes on Windows, some extra steps are required:
[all...] |
| /external/vulkan-validation-layers/tests/gtest-1.7.0/src/ |
| gtest-death-test.cc | 587 // implementation uses pipes for child-to-parent communication. But due to
588 // the specifics of pipes on Windows, some extra steps are required:
[all...] |
| /external/wpa_supplicant_8/wpa_supplicant/wpa_gui-qt4/ |
| wpagui.cpp | 817 * QSocketNotifier cannot be used with Windows named pipes, so use a
819 * optimized be doing something specific to named pipes or Windows
[all...] |
| /libcore/ojluni/src/main/java/java/lang/ |
| ProcessBuilder.java | 84 * output and standard error to pipes. Java code can access these pipes
[all...] |
| /prebuilts/ndk/r16/sources/third_party/googletest/googletest/src/ |
| gtest-death-test.cc | 587 // implementation uses pipes for child-to-parent communication. But due to
588 // the specifics of pipes on Windows, some extra steps are required:
[all...] |
| /cts/tests/tests/os/src/android/os/cts/ |
| MessageQueueTest.java | 284 // We don't actually care about the content (assume pipes work correctly)
[all...] |
| /developers/build/prebuilts/gradle/StorageProvider/Application/src/main/java/com/example/android/storageprovider/ |
| MyCloudProvider.java | 298 // transfer from the network, a better solution may be pipes or sockets
|
| /developers/samples/android/content/documentsUi/StorageProvider/Application/src/main/java/com/example/android/storageprovider/ |
| MyCloudProvider.java | 298 // transfer from the network, a better solution may be pipes or sockets
|
