Home
last modified time | relevance | path

Searched refs:macros (Results 1 – 25 of 36) sorted by relevance

12

/qemu/scripts/coccinelle/
H A Dqobject.cocci1 // Use QDict macros where they make sense
28 // Use QList macros where they make sense
/qemu/target/hexagon/
H A DREADME26 macros.def Mapping of macros to instruction attributes
40 macros inside the architecture definition files. This is done in
117 The instruction semantics C code relies heavily on macros. In cases where the
118 C semantics are specified only with macros, we can override the default with
119 the short semantics option and #define the macros to generate TCG code. One
211 macros.h
212 mmvec/macros.h
214 The Hexagon arch lib relies heavily on macros for the instruction semantics.
H A Dhex_common.py29 macros = {} # macro -> macro information... variable
63 if not macros[submacro]:
65 macro.attribs |= expand_macro_attribs(macros[submacro], allmac_re)
73 macros[name].attribs.add(attrib)
107 macroValues = list(macros.values())
117 macro = macros[macname]
160 macros[macname] = Macro(macname, beh, attribs)
/qemu/rust/bits/
H A DCargo.toml16 qemu_api_macros = { path = "../qemu-api-macros" }
/qemu/rust/qemu-api-macros/
H A DCargo.toml5 description = "Rust bindings for QEMU - Utility macros"
/qemu/rust/qemu-api/
H A DCargo.toml17 qemu_api_macros = { path = "../qemu-api-macros" }
H A DREADME.md3 This library exports helper Rust types, Rust macros and C FFI bindings for internal QEMU APIs.
/qemu/rust/hw/timer/hpet/
H A DCargo.toml18 qemu_api_macros = { path = "../../../qemu-api-macros" }
/qemu/rust/hw/char/pl011/
H A DCargo.toml23 qemu_api_macros = { path = "../../../qemu-api-macros" }
/qemu/docs/devel/
H A Drust.rst122 * ``qemu_api_macros`` defines several procedural macros that are useful when
329 variables. Often, unsafe traits can be generated by procedural macros.
349 Writing procedural macros
352 By conventions, procedural macros are split in two functions, one
383 Use procedural macros with care. They are mostly useful for two purposes:
394 Procedural macros can be hard to debug and test; if the code generation
396 "regular" declarative (``macro_rules!``) macros and write unit tests for
453 ``meson.override_dependency`` for dependencies of procedural macros.
454 If a crate is needed in both procedural macros and QEMU binaries, everything
H A Dstyle.rst274 Variadic macros
277 For variadic macros, stick with this C99-like syntax:
295 The "qemu/osdep.h" header contains preprocessor macros that affect the behavior
297 core system headers included by external libraries get the preprocessor macros
524 There are also replacement character processing macros for isxyz and toxyz,
580 The GLib2 library provides a number of functions/macros for enabling
695 since these are generated automatically by the QOM declaration macros.
698 QEMU GUARD macros
701 QEMU provides a number of ``_GUARD`` macros intended to make the
738 There are often ``WITH_`` forms of macros which more easily wrap
H A Dqom.rst107 :caption: Typecasting macros
305 Standard type declaration and definition macros
310 written for a new type there are two sets of macros to generate the
402 OBJECT_DEFINE_TYPE_WITH_INTERFACES() macros can be used instead.
H A Drcu.rst113 ``g_free_rcu`` macros, which handle the common case where the
180 Convenience macros
183 Two macros are provided that automatically release the read lock at the
/qemu/rust/
H A Dmeson.build23 subdir('qemu-api-macros')
H A DCargo.toml5 "qemu-api-macros",
/qemu/tests/tcg/xtensa/
H A DMakefile.softmmu-target34 $(XTENSA_USABLE_TESTS): linker.ld macros.inc $(CRT) Makefile.softmmu-target
/qemu/target/hexagon/imported/
H A Dallext_macros.def23 #include "mmvec/macros.def"
/qemu/rust/qemu-api-macros/src/
H A Dlib.rs195 #[rustfmt::skip::macros(quote)]
212 #[rustfmt::skip::macros(quote)]
/qemu/docs/devel/migration/
H A Dmain.rst150 Most device data can be described using the ``VMSTATE`` macros (mostly defined
189 The VMState macros take care of ensuring that the device data section
193 VMState macros can include other VMStateDescriptions to store substructures
195 arrays (``VMSTATE_VARRAY_``). Various other macros exist for special
224 Note that because the VMState macros still save the data in a raw
392 (see above) or _TEST macros (see above) which won't break compatibility.
406 There are *_V* forms of many ``VMSTATE_`` macros to load fields for version dependent fields,
484 The iterative devices generally don't use VMState macros
486 qemu_put_*/qemu_get_* macros to read/write data to the stream. Specialist
H A Dcompatibility.rst114 DEFINE_PROP_*() macros. See include/hw/qdev-properties.h to find the
115 macros that exist. With it, we set the default value for that
/qemu/target/hexagon/idef-parser/
H A DREADME.rst69 application of some macro definitions contained in the ``macros.h`` file.
138 with macros such as ``fJUMPR`` intact.
140 The second step is to expand macros into a form suitable for our parser.
141 These macros are defined in ``idef-parser/macros.h.inc`` and the step is
261 macros present in ``macros.h``. As an example, consider the ``fABS`` macro which
269 in ``idef-parser/macros.h.inc`` and as such is not expanded and kept as a "call"
272 macros in ``macros.h`` are kept unexpanded to aid in parsing, as seen in the
H A Dmacros.h.inc127 /* Include fHIDE macros which hide type declarations */
/qemu/include/exec/
H A Dhelper-info.c.inc14 * to get all the macros expanded first.
/qemu/docs/spin/
H A Dtcg-exclusive.promela16 * Tunable processor macros: N_CPUS, N_EXCLUSIVE, N_CYCLES, USE_MUTEX,
/qemu/ui/
H A Dvnc-enc-zrle.c.inc15 * Before including this file, you must define a number of CPP macros.

12