From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1JgP9F-0000Pu-HO
	for qemu-devel@nongnu.org; Mon, 31 Mar 2008 14:54:25 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1JgP9D-0000PQ-F0
	for qemu-devel@nongnu.org; Mon, 31 Mar 2008 14:54:24 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1JgP9D-0000PL-BU
	for qemu-devel@nongnu.org; Mon, 31 Mar 2008 14:54:23 -0400
Received: from gateway-1237.mvista.com ([63.81.120.158])
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <akuster@kama-aina.net>) id 1JgP9D-00079f-00
	for qemu-devel@nongnu.org; Mon, 31 Mar 2008 14:54:23 -0400
Received: from pahoa.hi.kama-aina.net (unknown [10.235.20.2])
	by hermes.mvista.com (Postfix) with ESMTP id 4C6E6187D7
	for <qemu-devel@nongnu.org>; Mon, 31 Mar 2008 11:54:12 -0700 (PDT)
Message-ID: <47F13353.3080504@kama-aina.net>
Date: Mon, 31 Mar 2008 08:54:11 -1000
From: Armin <akuster@kama-aina.net>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] ARM TCG conversion
References: <200803310458.53439.paul@codesourcery.com>
In-Reply-To: <200803310458.53439.paul@codesourcery.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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

Paul Brook wrote:
> I've just checked in a series of patches converting the ARM target to the new 
> TCG code generator.  All the dyngen ops have been removed.  The remaining 
> code is a muxture of explicit and implicit operands, so there's still some 
> cleanup to be done.
> 
> With the exception of fixing a couple of bugs in the SIMD instructions, the 
> code should be functionally identical.
> 
> If you do discover errors, it would be useful if you could track down exactly 
> which patch caused the failure, and preferable a reasonable sized 
> self-contained testcase. The code should still be functional at each of the 
> intermediate points.
> 
> Paul
> 
> 
> 
> 
Paul,

I am seeing two resource leak messages when booting the PXA27x 
mainstone. Not sure if this is the clean up you speak of. No I have not 
looked into which patches might be causing this, maybe I will be able to 
poke around some time this week.. The cvs sources from March 11 worked 
fine. yes, I know.. not very useful.


Uncompressing 
Linux........................................................................................................ 
done, booting the kernel.
Internal resource leak before c002fb08
...

XScale DSP coprocessor detected.
Internal resource leak before c002fb08

  -armin