/external/libmojo/ipc/ |
H A D | ipc_message_attachment.cc | 7 namespace IPC { namespace 15 } // namespace IPC
|
H A D | placeholder_brokerable_attachment.cc | 7 namespace IPC { namespace 14 } // namespace IPC
|
H A D | ipc_param_traits.h | 8 // Our IPC system uses the following partially specialized header to define how 9 // a data type is read, written and logged in the IPC system. 11 namespace IPC { namespace 21 } // namespace IPC
|
H A D | ipc_mojo_message_helper.h | 12 namespace IPC { namespace 27 } // namespace IPC
|
H A D | placeholder_brokerable_attachment.h | 12 namespace IPC { namespace 27 } // namespace IPC
|
H A D | ipc_listener.h | 13 namespace IPC { namespace 49 } // namespace IPC
|
H A D | ipc_message_attachment.h | 15 namespace IPC { namespace 41 } // namespace IPC
|
H A D | ipc_mojo_handle_attachment.cc | 11 namespace IPC { namespace 36 } // namespace IPC
|
H A D | ipc_mojo_handle_attachment.h | 15 namespace IPC { namespace 45 } // namespace IPC
|
H A D | ipc_mojo_param_traits.h | 20 namespace IPC { namespace 32 } // namespace IPC
|
H A D | ipc_platform_file_attachment_posix.cc | 9 namespace IPC { namespace 38 } // namespace IPC
|
H A D | ipc_platform_file_attachment_posix.h | 11 namespace IPC { namespace 41 } // namespace IPC
|
H A D | ipc_message_attachment_set.h | 21 namespace IPC { namespace 28 // associated with an IPC message. There are three types of MessageAttachments: 33 // Any given IPC Message can have attachments of type (1) or (2), but not both. 93 std::vector<scoped_refptr<IPC::BrokerableAttachment>> 161 } // namespace IPC
|
H A D | ipc_channel_handle.h | 19 // On Windows, any process can create an IPC channel and others can fetch 20 // it by name. We pass around the channel names over IPC. 23 // NOTE: A ChannelHandle with a pipe handle Will NOT be marshalled over IPC. 25 // On POSIX, we instead pass around handles to channel endpoints via IPC. 26 // When it's time to IPC a new channel endpoint around, we send both the 28 // type that knows how to copy a socket endpoint over IPC. 31 // in both Windows and Posix. When passing a handle to a channel over IPC, 34 namespace IPC { namespace 41 // Otherwise there may be a problem in IPC communication between 68 } // namespace IPC [all...] |
H A D | ipc_mojo_message_helper.cc | 11 namespace IPC { namespace 51 } // namespace IPC
|
H A D | brokerable_attachment.cc | 12 namespace IPC { namespace 72 } // namespace IPC
|
H A D | brokerable_attachment.h | 18 namespace IPC { namespace 21 // attached to a Chrome IPC message. 33 // the IPC translation system, which requires that classes have a default 89 } // namespace IPC
|
H A D | ipc_mojo_param_traits.cc | 10 namespace IPC { namespace 50 } // namespace IPC
|
H A D | ipc_sync_message.h | 20 namespace IPC { namespace 102 } // namespace IPC
|
/external/v8/tools/clang/plugins/tests/ |
H A D | ipc.cpp | 51 namespace IPC { namespace 68 } // namespace IPC 71 /* Test IPC::WriteParam() usage in templates. ERRORS: 6 */ 79 struct IPC::ParamTraits<Data> { 93 struct IPC::ParamTraits<Container<T>> { 96 IPC::WriteParam(pickle, container.value); // NOT CHECKED 100 IPC::WriteParam<T>(pickle, container.value); // NOT CHECKED 117 struct IPC::ParamTraits<MultiContainer<T, Ts...>> { 132 IPC::WriteParam(pickle, T(0)); // NOT CHECKED 135 IPC [all...] |
H A D | missing_ctor_ignored_base.h | 23 // IPC::NoParams is an ignored base. 24 namespace IPC { namespace 30 class MissingCtorsWithIgnoredBase : public IPC::NoParams {
|
/external/ltp/testcases/kernel/containers/ |
H A D | TEST_PLAN.txt | 23 POSIX IPC NAMESPACES (NEAR FUTURE)
|
/external/libmojo/mojo/public/cpp/bindings/lib/ |
H A D | native_enum_serialization.h | 25 using Traits = IPC::ParamTraits<UserType>;
|
/external/libmojo/mojo/public/cpp/bindings/tests/ |
H A D | pickled_types_blink.cc | 26 namespace IPC { namespace 67 } // namespace IPC
|
H A D | pickled_types_blink.h | 26 // Implementation of types with IPC::ParamTraits for consumers in Blink. 64 namespace IPC { namespace 78 } // namespace IPC
|