From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19WjSn-0004oV-OR
	for qemu-devel@nongnu.org; Sun, 29 Jun 2003 17:11:57 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19WjSG-0004Z9-7j
	for qemu-devel@nongnu.org; Sun, 29 Jun 2003 17:11:26 -0400
Received: from smtp3.wanadoo.fr ([193.252.22.25] helo=mwinf0604.wanadoo.fr)
	by monty-python.gnu.org with esmtp (Exim 4.20)
	id 19WjNH-0003MK-I5
	for qemu-devel@nongnu.org; Sun, 29 Jun 2003 17:06:15 -0400
Received: from free.fr (AMontpellier-205-1-20-58.w81-50.abo.wanadoo.fr
	[81.50.57.58])
	by mwinf0604.wanadoo.fr (SMTP Server) with ESMTP id 0D67D28000FA
	for <qemu-devel@nongnu.org>; Sun, 29 Jun 2003 23:06:14 +0200 (CEST)
Message-ID: <3EFF570D.2030502@free.fr>
Date: Sun, 29 Jun 2003 23:15:57 +0200
From: Fabrice Bellard <fabrice.bellard@free.fr>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] 64-bit target
References: <20030629144228.7e0ddebc.jrydberg@night.trouble.net>
	<3EFEE812.3020308@free.fr>
	<20030629203254.65b26caa.jrydberg@night.trouble.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Reply-To: qemu-devel@nongnu.org
List-Id: <qemu-devel.nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/qemu-devel>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
To: qemu-devel@nongnu.org

Johan Rydberg wrote:
> Fabrice Bellard <fabrice.bellard@free.fr> wrote:
> 
> : Johan Rydberg wrote:
> : > Hi,
> : > 
> : > what changes has to be done to make QEMU support 64-bit targets? 
> : > Any big overall changes needed at all?
> : 
> : No big changes, except that you must use a soft MMU if you want to use 
> : real 64 bit pointers.
> 
> After doing a little research it seems that dyngen can not cope with 
> 64-bit immediates.  ie PARAMn can only be as large as sizeof (void *).
> This must of course be fixed for a 64-bit target.  Any ideas how to
> fix it?

You can just use two parameters and load two 32 bit values.

Fabrice.