From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JAtZY-00028d-3z for qemu-devel@nongnu.org; Fri, 04 Jan 2008 15:55:20 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JAtZW-000258-ET for qemu-devel@nongnu.org; Fri, 04 Jan 2008 15:55:19 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JAtZW-00024m-6C for qemu-devel@nongnu.org; Fri, 04 Jan 2008 15:55:18 -0500 Received: from nf-out-0910.google.com ([64.233.182.186]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JAtZV-0004sY-To for qemu-devel@nongnu.org; Fri, 04 Jan 2008 15:55:18 -0500 Received: by nf-out-0910.google.com with SMTP id 30so550827nfu.12 for ; Fri, 04 Jan 2008 12:55:16 -0800 (PST) Message-ID: Date: Fri, 4 Jan 2008 22:55:15 +0200 From: "Blue Swirl" Subject: Re: [Qemu-devel] gen_op* function definitions In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: 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 1/4/08, Ryan W Smith wrote: > I'm trying to figure out how the translation blocks are generated and > I'm having a bit of difficulty. I'm trying to find and modify a > particular instruction rep ins*, which I've found and it looks like > it's being broken down into simpler instructions in the translation > process. I've followed it all the way down to the most basic > instructions, the first of which is gen_op_movl_A0_reg[EDI](), which > translates to gen_op_movl_A0_EDI(). This is where I'm stuck, I can't > find the definition for this function, or any of the gen_op* > instructions for that matter anywhere in the qemu source. I must be > missing something, can someone point me in the right direction to > find the definitions for the gen_op* functions. op.c is compiled and the resulting object file op.o is processed by dyngen program, producing gen-op.h, opc.h, and op.h. These define the gen_op* versions of the functions, originally op_something in op.c.