From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NK0f6-0000hZ-3s for qemu-devel@nongnu.org; Sun, 13 Dec 2009 21:27:48 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NK0f5-0000hF-Db for qemu-devel@nongnu.org; Sun, 13 Dec 2009 21:27:47 -0500 Received: from [199.232.76.173] (port=52835 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NK0f5-0000h1-5N for qemu-devel@nongnu.org; Sun, 13 Dec 2009 21:27:47 -0500 Received: from are.twiddle.net ([75.149.56.221]:56952) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NK0f3-0000N4-Hu for qemu-devel@nongnu.org; Sun, 13 Dec 2009 21:27:45 -0500 Received: from stone.twiddle.home (stone.twiddle.home [172.31.0.16]) by are.twiddle.net (Postfix) with ESMTPSA id 48781304 for ; Sun, 13 Dec 2009 18:27:44 -0800 (PST) Message-ID: <4B25A2A0.4060007@twiddle.net> Date: Sun, 13 Dec 2009 18:27:44 -0800 From: Richard Henderson MIME-Version: 1.0 Subject: Re: [Qemu-devel] TCGv_i64 type? References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org On 12/13/2009 06:00 PM, Jun Koi wrote: > I found that in tcg/tcg.h, we have following definitions: > > typedef int TCGv_i32; > typedef int TCGv_i64; > > Is that correct? Why do we have the same definition for 64bit and 32 > bit types? Doesnt TCGv_i64 suppose to be 64 bit? Look higher up in the DEBUG_TCGV section and you'll find typedef struct { int i32; } TCGv_i32; typedef struct { int i64; } TCGv_i64; which are separate types for type checking purposes. Both are "int" because at the TCG level these are register numbers. They are separate types because they indicate 32-bit or 64-bit quantities in the compiled code. r~