qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Jun Koi" <junkoi2004@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Questions on "hidden" functions in QEMU source code
Date: Tue, 16 Oct 2007 17:28:24 +0900	[thread overview]
Message-ID: <fdaac4d50710160128y14815bf1xc6f833cd428dc962@mail.gmail.com> (raw)

Hi,

I am looking at the source code of QEMU, and there are some mystery to
me: some functions are not defined anywhere.

For example, functions like compute_all_incb() and compute_c_incl() in
target-i386/op.c are never defined anywhere.

So how the compilation process generates these functions?

Another question: micro-op are defined as OPPROTO, but OPPROTO is
actually defined as empty in dyngen-exec.h

#define OPPROTO

So what is the point of using OPPROTO here? I am sure that there is a
good reason to do that, but cannot figure it out.

Many thanks,
Jun

             reply	other threads:[~2007-10-16  8:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-16  8:28 Jun Koi [this message]
2007-10-16 13:42 ` [Qemu-devel] Questions on "hidden" functions in QEMU source code Stuart Brady
2007-10-16 14:19   ` Johannes Schindelin
2007-10-18  2:46     ` Jun Koi
2007-10-20  7:02     ` Rob Landley

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=fdaac4d50710160128y14815bf1xc6f833cd428dc962@mail.gmail.com \
    --to=junkoi2004@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).