glib/gio/gmarshal-internal.list

BOOLEAN:OBJECT
BOOLEAN:OBJECT,FLAGS
BOOLEAN:OBJECT,OBJECT
BOOLEAN:POINTER,INT
BOOLEAN:STRING
BOOLEAN:UINT
BOOLEAN:VOID
INT:BOXED
INT:OBJECT
VOID:BOOLEAN,BOXED
VOID:ENUM,OBJECT
VOID:ENUM,OBJECT,OBJECT
VOID:INT,INT,INT
VOID:OBJECT,OBJECT
VOID:OBJECT,OBJECT,ENUM
VOID:OBJECT,OBJECT,STRING,STRING,VARIANT
VOID:OBJECT,OBJECT,VARIANT,BOXED
VOID:OBJECT,VARIANT
VOID:POINTER,INT,STRING
VOID:STRING,BOOLEAN
VOID:STRING,BOXED
VOID:STRING,BOXED,BOXED
VOID:STRING,INT64,INT64
VOID:STRING,STRING,STRING,FLAGS
VOID:STRING,STRING,VARIANT
VOID:STRING,VARIANT
VOID:UINT,UINT,UINT
VOID:VARIANT,BOXED
gio: remove use of generic marshaller from GIO objects Using the generic marshaller has drawbacks beyond performance. One such drawback is that it breaks the stack unwinding from the Linux kernel due to having unsufficient data to walk past ffi_call_unixt64. That means that performance profiling by application developers looks grouped among seemingly unrelated code paths. While we can't fix the kernel unwinding here, we can provide proper c_marshallers and va_marshallers for objects within Gio so that performance profiling of applications is more reliable. Related to GNOME/Initiatives#10 2019-05-31 04:29:18 +02:00			`BOOLEAN:OBJECT`
			`BOOLEAN:OBJECT,FLAGS`
			`BOOLEAN:OBJECT,OBJECT`
			`BOOLEAN:POINTER,INT`
			`BOOLEAN:STRING`
			`BOOLEAN:UINT`
			`BOOLEAN:VOID`
			`INT:BOXED`
			`INT:OBJECT`
			`VOID:BOOLEAN,BOXED`
			`VOID:ENUM,OBJECT`
			`VOID:ENUM,OBJECT,OBJECT`
			`VOID:INT,INT,INT`
			`VOID:OBJECT,OBJECT`
			`VOID:OBJECT,OBJECT,ENUM`
			`VOID:OBJECT,OBJECT,STRING,STRING,VARIANT`
			`VOID:OBJECT,OBJECT,VARIANT,BOXED`
			`VOID:OBJECT,VARIANT`
			`VOID:POINTER,INT,STRING`
			`VOID:STRING,BOOLEAN`
			`VOID:STRING,BOXED`
			`VOID:STRING,BOXED,BOXED`
			`VOID:STRING,INT64,INT64`
			`VOID:STRING,STRING,STRING,FLAGS`
			`VOID:STRING,STRING,VARIANT`
			`VOID:STRING,VARIANT`
			`VOID:UINT,UINT,UINT`
			`VOID:VARIANT,BOXED`