From: Stefan Hajnoczi <stefanha@gmail.com>
To: "陳韋任 (Wei-Ren Chen)" <chenwj@iis.sinica.edu.tw>
Cc: qemu-trivial@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Use proper term in TCG README
Date: Fri, 8 Mar 2013 10:21:02 +0100 [thread overview]
Message-ID: <20130308092102.GD9597@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <20130307033301.GA48996@cs.nctu.edu.tw>
On Thu, Mar 07, 2013 at 11:33:01AM +0800, 陳韋任 (Wei-Ren Chen) wrote:
> In TCG, "target" means the host architecture for which TCG generates the
> code. Using "guest" rather than "target" to make the document more consistent.
>
> Signed-off-by: Chen Wei-Ren <chenwj@iis.sinica.edu.tw>
> ---
> tcg/README | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tcg/README b/tcg/README
> index 934e7af..22174c0 100644
> --- a/tcg/README
> +++ b/tcg/README
> @@ -379,7 +379,7 @@ double-word product T0. The later is returned in two single-word outputs.
>
> Similar to mulu2, except the two inputs T1 and T2 are signed.
>
> -********* 64-bit target on 32-bit host support
> +********* 64-bit guest on 32-bit host support
>
> The following opcodes are internal to TCG. Thus they are to be implemented by
> 32-bit host code generators, but are not to be emitted by guest translators.
Review from TCG experts please.
It seems we have multiple meanings for "target" (e.g. ./configure
--target-list= does not mean "the host architecture for which TCG
generates code"), if this is really the way TCG uses the term then fine.
Stefan
next prev parent reply other threads:[~2013-03-08 9:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-07 3:33 [Qemu-devel] [PATCH] Use proper term in TCG README 陳韋任 (Wei-Ren Chen)
2013-03-08 9:21 ` Stefan Hajnoczi [this message]
2013-03-08 9:29 ` Peter Maydell
2013-03-08 10:13 ` Stefan Hajnoczi
2013-03-14 6:27 ` 陳韋任 (Wei-Ren Chen)
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=20130308092102.GD9597@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=chenwj@iis.sinica.edu.tw \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).