Lines Matching refs:C

21 together with the C code.  This is completely automatic when you run
68 they need support C code from QEMU that Cargo does not know about.  Tests can
120 * ``qemu_api`` for bindings to C code and useful functionality
123   writing C code
142   full functionality available in C
176   API stability is not a promise, if anything because the C APIs are not a stable
183 C function names usually are prefixed according to the data type that they
272 Whenever C code provides you with an opaque ``void *``, avoid converting it
288 a raw pointer, for use in calls to C functions.  It can be used for
303 Writing bindings to C code
309   Very often, similar idioms in C code correspond to similar tricks in
310   Rust bindings.  If the C code uses ``offsetof``, look at qdev properties
311   or ``vmstate``.  If the C code has a complex const struct, look at
319   (either a builtin one or a user-defined one) in order to pass it to C
327   by generic functions.  C code usually places metadata in global variables;
386   that the structure has ``#[repr[C])`` and that the type of the first field