From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33)
	id 1BcCOy-0005dS-I0
	for qemu-devel@nongnu.org; Sun, 20 Jun 2004 20:11:08 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33)
	id 1BcCOx-0005cq-7V
	for qemu-devel@nongnu.org; Sun, 20 Jun 2004 20:11:07 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.33) id 1BcCOw-0005cR-OK
	for qemu-devel@nongnu.org; Sun, 20 Jun 2004 20:11:06 -0400
Received: from [216.254.0.205] (helo=mail5.speakeasy.net)
	by monty-python.gnu.org with esmtp (TLSv1:DES-CBC3-SHA:168)
	(Exim 4.34) id 1BcCMx-0003C0-2b
	for qemu-devel@nongnu.org; Sun, 20 Jun 2004 20:09:03 -0400
Received: from dsl081-088-222.lax1.dsl.speakeasy.net (HELO [192.168.111.2])
	([64.81.88.222]) (envelope-sender <jhoger@speakeasy.net>)
	by mail5.speakeasy.net (qmail-ldap-1.03) with SMTP
	for <qemu-devel@nongnu.org>; 21 Jun 2004 00:09:01 -0000
Subject: Re: [Qemu-devel] help porting to BF533
From: "John R. Hogerhuis" <jhoger@speakeasy.net>
In-Reply-To: <32848.81.199.255.141.1087770276.squirrel@81.199.255.141>
References: <32848.81.199.255.141.1087770276.squirrel@81.199.255.141>
Content-Type: text/plain
Message-Id: <1087776546.21945.201.camel@aragorn>
Mime-Version: 1.0
Date: Sun, 20 Jun 2004 17:09:06 -0700
Content-Transfer-Encoding: 7bit
Reply-To: jhoger@pobox.com, 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

dyngen must be ported to at least one library format per processor QEMU
is used with.

For example, on x86, ELF would have been enough. Generate the code to
ELF, then it must be read back in so that the lengths of each code block
and relocation information can be determined.

The folks that did the Windows port went the extra mile and ported
dyngen to COFF.

In fact it would be completely reasonable to use the dynamically
generated primitives from a Linux ELF file on a COFF platform.

However, I don't know anything about the Blackfin BF533 and bflt.

My guess is you will have to completely port dyngen over to that
platform. I see you becoming intimately familiar with bflt in the near
future :-)

-- John.