Home
last modified time | relevance | path

Searched refs:marshalling (Results 1 – 20 of 20) sorted by relevance

/third_party/skia/third_party/externals/abseil-cpp/absl/flags/
DBUILD.bazel89 name = "marshalling",
91 "marshalling.cc",
94 "marshalling.h",
203 ":marshalling",
364 ":marshalling",
389 ":marshalling",
408 ":marshalling",
474 ":marshalling",
DBUILD.gn53 absl_source_set("marshalling") {
54 sources = [ "marshalling.cc" ]
55 public = [ "marshalling.h" ]
127 ":marshalling",
DCMakeLists.txt79 "marshalling.cc"
81 "marshalling.h"
/third_party/python/Doc/c-api/
Dmarshal.rst5 Data marshalling support
/third_party/python/Doc/library/
Dxmlrpc.client.rst263 use by the marshalling/unmarshalling code:
324 internal use by the marshalling/unmarshalling code:
393 # A marshalling error is going to occur because we're returning a
Dmarshal.rst132 Modula-3 (amongst others), who use the term "marshalling" for shipping of data
Dpickle.rst16 pair: marshalling; objects
28 known as "serialization", "marshalling," [#]_ or "flattening"; however, to
1122 alternatives such as the marshalling API in :mod:`xmlrpc.client` or
Dlogging.handlers.rst1105 override this method if you need to do any custom marshalling or
/third_party/jsframework/runtime/main/extend/systemplugin/napi/
Dohos_rpc.js666 marshalling: function (...args) { method
/third_party/skia/third_party/externals/abseil-cpp/absl/base/
DBUILD.bazel701 "//absl/flags:marshalling",
/third_party/python/
DMakefile.pre.in1215 # In the past, we've had problems where bugs in the marshalling or
/third_party/mesa3d/docs/relnotes/
D20.1.0.rst3007 - glthread: replace custom ClearBuffer marshalling with generated one
3022 - glthread: replace custom glBindBuffer marshalling with generated one
3027 - glthread: add custom marshalling for glNamedBuffer(Sub)DataEXT
/third_party/python/Doc/whatsnew/
D2.3.rst1565 widget is accessed from a different thread by marshalling a command, passing it
/third_party/gstreamer/gstreamer/docs/random/
DChangeLog-0.88503 Change the marshalling of element_added/element_removed
/third_party/gstreamer/gstreamer/docs/random/old/
DChangeLog.gstreamer981 I don't pretend to understand how the marshalling stuff works - I
/third_party/python/Misc/
DHISTORY4486 - Issue #5308: Raise ValueError when marshalling too large object (a sequence
8211 - Issue #14172: Fix reference leak when marshalling a buffer-like object
/third_party/gstreamer/gstplugins_base/
DChangeLog12228 signal emission a bit more performant than the regular marshalling,
26575 Execute GL calls without marshalling them to the context thread. In the cocoa
26578 more efficient (faster and has less overhead) than marshalling everything to the
27214 This is simply a convenience to avoid duplicating the thread marshalling on
27618 Performing any GL function marshalling off the GL thread with glimagesink's
27624 4. As the GL function marshalling is attempting to run on the GL
/third_party/gstreamer/gstplugins_bad/
DChangeLog33206 signal emission a bit more performant than the regular marshalling,
76618 Execute GL calls without marshalling them to the context thread. In the cocoa
76621 more efficient (faster and has less overhead) than marshalling everything to the
80529 This is simply a convenience to avoid duplicating the thread marshalling on
81865 Performing any GL function marshalling off the GL thread with glimagesink's
81871 4. As the GL function marshalling is attempting to run on the GL
/third_party/gstreamer/gstreamer/
DChangeLog7120 signal emission a bit more performant than the regular marshalling,
128683 …gst/elements/gstidentity.c (marshal_VOID__MINIOBJECT): Write our own marshalling function for the …
128687 own marshalling function for the handoff signal. Properly type the
/third_party/gstreamer/gstplugins_good/
DChangeLog11729 signal emission a bit more performant than the regular marshalling,
22317 So instead of marshalling buffers through three layers and back,
24626 So instead of marshalling buffers through three layers and back,