Searched refs:IPC (Results 1 - 25 of 37) sorted by relevance

12

/external/libmojo/ipc/
H A Dipc_message_attachment.cc7 namespace IPC { namespace
15 } // namespace IPC
H A Dplaceholder_brokerable_attachment.cc7 namespace IPC { namespace
14 } // namespace IPC
H A Dipc_param_traits.h8 // 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 Dipc_mojo_message_helper.h12 namespace IPC { namespace
27 } // namespace IPC
H A Dplaceholder_brokerable_attachment.h12 namespace IPC { namespace
27 } // namespace IPC
H A Dipc_listener.h13 namespace IPC { namespace
49 } // namespace IPC
H A Dipc_message_attachment.h15 namespace IPC { namespace
41 } // namespace IPC
H A Dipc_mojo_handle_attachment.cc11 namespace IPC { namespace
36 } // namespace IPC
H A Dipc_mojo_handle_attachment.h15 namespace IPC { namespace
45 } // namespace IPC
H A Dipc_mojo_param_traits.h20 namespace IPC { namespace
32 } // namespace IPC
H A Dipc_platform_file_attachment_posix.cc9 namespace IPC { namespace
38 } // namespace IPC
H A Dipc_platform_file_attachment_posix.h11 namespace IPC { namespace
41 } // namespace IPC
H A Dipc_message_attachment_set.h21 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 Dipc_channel_handle.h19 // 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 Dipc_mojo_message_helper.cc11 namespace IPC { namespace
51 } // namespace IPC
H A Dbrokerable_attachment.cc12 namespace IPC { namespace
72 } // namespace IPC
H A Dbrokerable_attachment.h18 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 Dipc_mojo_param_traits.cc10 namespace IPC { namespace
50 } // namespace IPC
H A Dipc_sync_message.h20 namespace IPC { namespace
102 } // namespace IPC
/external/v8/tools/clang/plugins/tests/
H A Dipc.cpp51 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 Dmissing_ctor_ignored_base.h23 // IPC::NoParams is an ignored base.
24 namespace IPC { namespace
30 class MissingCtorsWithIgnoredBase : public IPC::NoParams {
/external/ltp/testcases/kernel/containers/
H A DTEST_PLAN.txt23 POSIX IPC NAMESPACES (NEAR FUTURE)
/external/libmojo/mojo/public/cpp/bindings/lib/
H A Dnative_enum_serialization.h25 using Traits = IPC::ParamTraits<UserType>;
/external/libmojo/mojo/public/cpp/bindings/tests/
H A Dpickled_types_blink.cc26 namespace IPC { namespace
67 } // namespace IPC
H A Dpickled_types_blink.h26 // Implementation of types with IPC::ParamTraits for consumers in Blink.
64 namespace IPC { namespace
78 } // namespace IPC

Completed in 401 milliseconds

12