From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1IiLPX-0007os-2q
	for qemu-devel@nongnu.org; Wed, 17 Oct 2007 22:46:59 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1IiLPV-0007oS-Nr
	for qemu-devel@nongnu.org; Wed, 17 Oct 2007 22:46:58 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1IiLPV-0007oP-IZ
	for qemu-devel@nongnu.org; Wed, 17 Oct 2007 22:46:57 -0400
Received: from wa-out-1112.google.com ([209.85.146.182])
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <junkoi2004@gmail.com>) id 1IiLPU-0000LF-2u
	for qemu-devel@nongnu.org; Wed, 17 Oct 2007 22:46:57 -0400
Received: by wa-out-1112.google.com with SMTP id k22so44043waf
	for <qemu-devel@nongnu.org>; Wed, 17 Oct 2007 19:46:48 -0700 (PDT)
Message-ID: <fdaac4d50710171946p523871f0y167b147afb9ea27a@mail.gmail.com>
Date: Thu, 18 Oct 2007 11:46:47 +0900
From: "Jun Koi" <junkoi2004@gmail.com>
Subject: Re: [Qemu-devel] Questions on "hidden" functions in QEMU source code
In-Reply-To: <Pine.LNX.4.64.0710161518460.25221@racer.site>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <fdaac4d50710160128y14815bf1xc6f833cd428dc962@mail.gmail.com>
	<20071016134256.GA31792@miranda.arrow>
	<Pine.LNX.4.64.0710161518460.25221@racer.site>
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

On 10/16/07, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> Hi,
>
> On Tue, 16 Oct 2007, Stuart Brady wrote:
>
> > 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.
>
> If you wonder why it is included four times, this might help:
>
> http://libvncserver.sourceforge.net/qemu/qemu-templates-ala-Fabrice.txt
>

Now it is clear that those stuffs are generated by dyngen, thanks.

But still it it not obvious to me what is the purpose of "OPPROTO"
when defining micro-ops. May you elaborate this a bit more?

Many thanks,
Jun
> Hth,
> Dscho
>
>
>
>