From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IhmhP-0004Zs-RA for qemu-devel@nongnu.org; Tue, 16 Oct 2007 09:43:07 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IhmhN-0004Za-9U for qemu-devel@nongnu.org; Tue, 16 Oct 2007 09:43:06 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IhmhN-0004ZW-4j for qemu-devel@nongnu.org; Tue, 16 Oct 2007 09:43:05 -0400 Received: from mtaout02-winn.ispmail.ntl.com ([81.103.221.48]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1IhmhM-0003oF-Lq for qemu-devel@nongnu.org; Tue, 16 Oct 2007 09:43:04 -0400 Received: from aamtaout03-winn.ispmail.ntl.com ([81.103.221.35]) by mtaout02-winn.ispmail.ntl.com with ESMTP id <20071016134259.EOBY25022.mtaout02-winn.ispmail.ntl.com@aamtaout03-winn.ispmail.ntl.com> for ; Tue, 16 Oct 2007 14:42:59 +0100 Received: from miranda.arrow ([213.107.26.151]) by aamtaout03-winn.ispmail.ntl.com with ESMTP id <20071016134259.EXJS26699.aamtaout03-winn.ispmail.ntl.com@miranda.arrow> for ; Tue, 16 Oct 2007 14:42:59 +0100 Received: from sdb by miranda.arrow with local (Exim 4.63) (envelope-from ) id 1IhmhF-0008H0-50 for qemu-devel@nongnu.org; Tue, 16 Oct 2007 14:42:57 +0100 Date: Tue, 16 Oct 2007 14:42:56 +0100 From: Stuart Brady Subject: Re: [Qemu-devel] Questions on "hidden" functions in QEMU source code Message-ID: <20071016134256.GA31792@miranda.arrow> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org 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