From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1L25MK-0001eW-Hi
	for qemu-devel@nongnu.org; Mon, 17 Nov 2008 09:45:48 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1L25MJ-0001eC-9e
	for qemu-devel@nongnu.org; Mon, 17 Nov 2008 09:45:48 -0500
Received: from [199.232.76.173] (port=42721 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1L25MJ-0001e9-64
	for qemu-devel@nongnu.org; Mon, 17 Nov 2008 09:45:47 -0500
Received: from mail.codesourcery.com ([65.74.133.4]:60889)
	by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60)
	(envelope-from <paul@codesourcery.com>) id 1L25MI-0008PC-KE
	for qemu-devel@nongnu.org; Mon, 17 Nov 2008 09:45:46 -0500
From: Paul Brook <paul@codesourcery.com>
Date: Mon, 17 Nov 2008 14:45:40 +0000
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200811171445.40710.paul@codesourcery.com>
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: [Qemu-devel] TCG debugging improvements
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

I'd just applied changes that enforce type size checking for TCG variables 
when DEBUG_TCGV is defined. This should help avoid subtle bugs due to 
64/32-bit mismatches.

I fixed a few bugs in the process, but it's mostly mechanical changes.  TCGv 
is target_ulong sized, so the majority of code remains unchanged.  Explicit 
sizes are typically only required when working with different sized ops, or 
floating point.

One of the main side-effects of this is that helper functions now need to be 
declared properly.  Previously we sort-of did this, but not consistently 
enough to enforce types.  With the exception of the SSE/MMX ops (which are 
table driven and use messy typecasts) we should be able to detect 
inconsistencies between the code generator and the helper function 
implementations.

There should be no functional changes.  I've tested what I can, but please 
test your favourite host/target.

Paul