From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Ihhmu-0007go-KX for qemu-devel@nongnu.org; Tue, 16 Oct 2007 04:28:28 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Ihhms-0007gb-CL for qemu-devel@nongnu.org; Tue, 16 Oct 2007 04:28:27 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ihhms-0007gY-6n for qemu-devel@nongnu.org; Tue, 16 Oct 2007 04:28:26 -0400 Received: from nz-out-0506.google.com ([64.233.162.232]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Ihhmr-0001j2-U7 for qemu-devel@nongnu.org; Tue, 16 Oct 2007 04:28:26 -0400 Received: by nz-out-0506.google.com with SMTP id f1so4416365nzc for ; Tue, 16 Oct 2007 01:28:25 -0700 (PDT) Message-ID: Date: Tue, 16 Oct 2007 17:28:24 +0900 From: "Jun Koi" MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: [Qemu-devel] Questions on "hidden" functions in QEMU source code 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 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