From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=45338 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1PcKyh-00022q-Es
	for qemu-devel@nongnu.org; Mon, 10 Jan 2011 11:52:20 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <aurelien@aurel32.net>) id 1PcKye-0006F0-QY
	for qemu-devel@nongnu.org; Mon, 10 Jan 2011 11:52:19 -0500
Received: from hall.aurel32.net ([88.191.126.93]:40935)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <aurelien@aurel32.net>) id 1PcKye-0006Eu-La
	for qemu-devel@nongnu.org; Mon, 10 Jan 2011 11:52:16 -0500
Date: Mon, 10 Jan 2011 17:52:15 +0100
From: Aurelien Jarno <aurelien@aurel32.net>
Subject: Re: [Qemu-devel] Re: [PATCH 5/7] tcg-i386: Implement deposit
	operation.
Message-ID: <20110110165215.GJ17026@hall.aurel32.net>
References: <1294440183-885-1-git-send-email-rth@twiddle.net>
	<1294440183-885-6-git-send-email-rth@twiddle.net>
	<20110109215335.GA21189@volta.aurel32.net>
	<4D2A3CD1.2050003@twiddle.net>
	<20110110001610.GB17026@hall.aurel32.net>
	<4D2A562A.7000806@twiddle.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-15
Content-Disposition: inline
In-Reply-To: <4D2A562A.7000806@twiddle.net>
Sender: Aurelien Jarno <aurelien@aurel32.net>
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.nongnu.org/archive/html/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: Richard Henderson <rth@twiddle.net>
Cc: qemu-devel@nongnu.org, Alexander Graf <agraf@suse.de>

On Sun, Jan 09, 2011 at 04:43:22PM -0800, Richard Henderson wrote:
> On 01/09/2011 04:16 PM, Aurelien Jarno wrote:
> > The code being written now or latter doesn't change the question to know
> > if it is always possible to allocate one scratch register here on i386.
> 
> Yes.
> 
> Here there's only one register that needs to remain live.  In the 
> worst case, we'll spill one live register.  Which we can always do
> via a simple store via AREG0 + offset.

Oh right correct we are inside the instruction and in a case we have
very few arguments, and only 32-bit.

If we allow the target to allocate scratch registers themselves, it's
probably better to do that via a function.

-- 
Aurelien Jarno	                        GPG: 1024D/F1BCDB73
aurelien@aurel32.net                 http://www.aurel32.net