From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH 04/10] qemu-tech: move text from qemu-tech to tcg/README
Date: Thu, 6 Oct 2016 17:24:17 +0200 [thread overview]
Message-ID: <1475767463-12045-5-git-send-email-pbonzini@redhat.com> (raw)
In-Reply-To: <1475767463-12045-1-git-send-email-pbonzini@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
---
qemu-tech.texi | 12 ++----------
tcg/README | 5 +++++
2 files changed, 7 insertions(+), 10 deletions(-)
diff --git a/qemu-tech.texi b/qemu-tech.texi
index 2ab7cd4..082b62c 100644
--- a/qemu-tech.texi
+++ b/qemu-tech.texi
@@ -287,16 +287,8 @@ are very complicated and highly CPU dependent. QEMU uses some tricks
which make it relatively easily portable and simple while achieving good
performances.
-After the release of version 0.9.1, QEMU switched to a new method of
-generating code, Tiny Code Generator or TCG. TCG relaxes the
-dependency on the exact version of the compiler used. The basic idea
-is to split every target instruction into a couple of RISC-like TCG
-ops (see @code{target-i386/translate.c}). Some optimizations can be
-performed at this stage, including liveness analysis and trivial
-constant expression evaluation. TCG ops are then implemented in the
-host CPU back end, also known as TCG target (see
-@code{tcg/i386/tcg-target.inc.c}). For more information, please take a
-look at @code{tcg/README}.
+QEMU's dynamic translation backend is called TCG, for "Tiny Code
+Generator". For more information, please take a look at @code{tcg/README}.
@node Condition code optimisations
@section Condition code optimisations
diff --git a/tcg/README b/tcg/README
index 1d48aa9..ae31388 100644
--- a/tcg/README
+++ b/tcg/README
@@ -8,6 +8,11 @@ in the QOP code generator written by Paul Brook.
2) Definitions
+TCG receives RISC-like "TCG ops" and performs some optimizations on them,
+including liveness analysis and trivial constant expression
+evaluation. TCG ops are then implemented in the host CPU back end,
+also known as the TCG "target".
+
The TCG "target" is the architecture for which we generate the
code. It is of course not the same as the "target" of QEMU which is
the emulated architecture. As TCG started as a generic C backend used
--
2.7.4
next prev parent reply other threads:[~2016-10-06 15:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-06 15:24 [Qemu-devel] [PATCH 00/10] qemu-tech cleanup Paolo Bonzini
2016-10-06 15:24 ` [Qemu-devel] [PATCH 01/10] qemu-tech: drop index Paolo Bonzini
2016-10-06 15:24 ` [Qemu-devel] [PATCH 02/10] qemu-doc: replace introduction with the one from the internals manual Paolo Bonzini
2016-10-06 15:24 ` [Qemu-devel] [PATCH 03/10] qemu-doc: drop installation and compilation notes Paolo Bonzini
2016-10-06 15:24 ` Paolo Bonzini [this message]
2016-10-06 15:24 ` [Qemu-devel] [PATCH 05/10] qemu-tech: document lazy condition code evaluation in cpu.h Paolo Bonzini
2016-10-06 16:18 ` Emilio G. Cota
2016-10-06 16:21 ` Paolo Bonzini
2016-10-06 18:45 ` Peter Maydell
2016-10-07 8:02 ` Paolo Bonzini
2016-10-06 15:24 ` [Qemu-devel] [PATCH 06/10] qemu-tech: move user mode emulation features from qemu-tech Paolo Bonzini
2016-10-06 18:32 ` Jonathan Neuschäfer
2016-10-07 7:55 ` Paolo Bonzini
2016-10-06 15:24 ` [Qemu-devel] [PATCH 07/10] qemu-tech: move TCG test documentation to tests/tcg/README Paolo Bonzini
2016-10-06 15:24 ` [Qemu-devel] [PATCH 08/10] qemu-tech: reorganize content Paolo Bonzini
2016-10-06 15:24 ` [Qemu-devel] [PATCH 09/10] qemu-tech: rewrite some parts Paolo Bonzini
2016-10-06 16:31 ` Emilio G. Cota
2016-10-07 7:55 ` Paolo Bonzini
2016-10-06 15:24 ` [Qemu-devel] [PATCH 10/10] qemu-doc: merge qemu-tech and qemu-doc Paolo Bonzini
2016-10-06 16:36 ` [Qemu-devel] [PATCH 00/10] qemu-tech cleanup Emilio G. Cota
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1475767463-12045-5-git-send-email-pbonzini@redhat.com \
--to=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).