Documentation/TCG: Difference between revisions
(Update links) |
|||
| Line 14: | Line 14: | ||
* Details about {{src|path=docs/devel/tcg.rst|translator internals}} | * Details about {{src|path=docs/devel/tcg.rst|translator internals}} | ||
* Notes on {{src|path=docs/devel/decodetree.rst|description=decodetree}} (used by newer frontends to reduce boilerplate) | * Notes on {{src|path=docs/devel/decodetree.rst|description=decodetree}} (used by newer frontends to reduce boilerplate) | ||
* How we approach {{src|path=docs/devel/multi-thread-tcg. | * How we approach {{src|path=docs/devel/multi-thread-tcg.txt|description=multithreaded TCG}} | ||
== Other pages on the wiki == | == Other pages on the wiki == | ||
Latest revision as of 09:42, 5 November 2019
Tiny Code Generator (TCG)
The Tiny Code Generator (TCG) exists to transform target insns (the processor being emulated) via the TCG frontend to TCG ops which are then transformed into host insns (the processor executing QEMU itself) via the TCG backend.
People who wish to port QEMU to run on a new processor need to be concerned with the backend. There also exists the TCI (TCG Interpreter) effort which provides a backend agnostic interpreter for TCGops.
People who wish to port QEMU to emulate a new processor need to be concerned with the frontend.
Source Tree Documentation
A number of documents in the source tree should be helpful to understanding how things go together:
- The intro README
- Details about docs/devel/tcg.rst
- Notes on decodetree (used by newer frontends to reduce boilerplate)
- How we approach multithreaded TCG
Other pages on the wiki
Presentations and Other External Sources
- Slides and recording of a talk on TCG mechanics
- StackOverflow answer showing code flow of a TCG translation