From: Stuart Brady <sdbrady@ntlworld.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Questions on "hidden" functions in QEMU source code
Date: Tue, 16 Oct 2007 14:42:56 +0100 [thread overview]
Message-ID: <20071016134256.GA31792@miranda.arrow> (raw)
In-Reply-To: <fdaac4d50710160128y14815bf1xc6f833cd428dc962@mail.gmail.com>
On Tue, Oct 16, 2007 at 05:28:24PM +0900, Jun Koi wrote:
> For example, functions like compute_all_incb() and compute_c_incl() in
> target-i386/op.c are never defined anywhere.
compute_all_inc* are defined in ops_template.h:~171. You'll notice that
ops_template.h is included four times from op.c.
> 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.
Presumably so that attributes can be defined later if they're needed.
Cheers,
--
Stuart Brady
next prev parent reply other threads:[~2007-10-16 13:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-16 8:28 [Qemu-devel] Questions on "hidden" functions in QEMU source code Jun Koi
2007-10-16 13:42 ` Stuart Brady [this message]
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=20071016134256.GA31792@miranda.arrow \
--to=sdbrady@ntlworld.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.