qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Richard Henderson <rth@twiddle.net>
To: Gaurav Sharma <gauravs.2010@gmail.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [TCG] : Code flow understanding
Date: Fri, 07 Feb 2014 12:55:41 -0800	[thread overview]
Message-ID: <52F5484D.70804@twiddle.net> (raw)
In-Reply-To: <CABiB5K7jG0oacV2odzCQWBHKwW-skvhb=iEUO4GtiQUniBq2nA@mail.gmail.com>

On 02/05/2014 11:22 PM, Gaurav Sharma wrote:
> I need some help regarding the flow of generating a TCG op and then
> subsequent translation of any op into target instrn.

That's most of tcg/tcg.c and tcg/foo/tcg-target.c.

tcg_gen_code is the main entry point for beginning the compilation
of the previously emitted tcg ops.


r~

  reply	other threads:[~2014-02-07 20:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-06  7:22 [Qemu-devel] [TCG] : Code flow understanding Gaurav Sharma
2014-02-07 20:55 ` Richard Henderson [this message]
2014-02-10  9:46   ` Gaurav Sharma
2014-02-10 11:04     ` Peter Maydell
2014-02-10 12:11       ` Gaurav Sharma
2014-02-10 14:28         ` Gaurav Sharma

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=52F5484D.70804@twiddle.net \
    --to=rth@twiddle.net \
    --cc=gauravs.2010@gmail.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).