Documentation/TCG: Difference between revisions

From QEMU
(It's unlikely the TCI will replace generated code anytime soon.)
Line 3: Line 3:
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.
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. Although this whole exercise might be obsoleted by the [[Features/TCI|TCI (TCG Interpreter)]] effort.
People who wish to port QEMU to run on a new processor need to be concerned with the backend. There also exists the [[Features/TCI|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.
People who wish to port QEMU to emulate a new processor need to be concerned with the frontend.

Revision as of 09:33, 15 April 2016

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.