From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1DNvAA-00077R-9S for qemu-devel@nongnu.org; Tue, 19 Apr 2005 12:01:22 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1DNvA7-00076M-Vd for qemu-devel@nongnu.org; Tue, 19 Apr 2005 12:01:21 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DNvA7-0006Rz-Ni for qemu-devel@nongnu.org; Tue, 19 Apr 2005 12:01:19 -0400 Received: from [195.130.132.58] (helo=astra.telenet-ops.be) by monty-python.gnu.org with esmtp (Exim 4.34) id 1DNv4u-0000q1-3G for qemu-devel@nongnu.org; Tue, 19 Apr 2005 11:55:56 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by astra.telenet-ops.be (Postfix) with SMTP id 7F751328198 for ; Tue, 19 Apr 2005 17:53:44 +0200 (MEST) Received: from [192.168.1.2] (d51A51CF1.access.telenet.be [81.165.28.241]) by astra.telenet-ops.be (Postfix) with ESMTP id 5C1D2328186 for ; Tue, 19 Apr 2005 17:53:44 +0200 (MEST) Subject: Re: [Qemu-devel] Possible?: statically converting i386 ELF object files to ARM ELF object files From: Bob Deblier In-Reply-To: <4264CAFD.9050008@gmail.com> References: <4264CAFD.9050008@gmail.com> Content-Type: text/plain Date: Tue, 19 Apr 2005 17:53:44 +0200 Message-Id: <1113926024.4762.13.camel@orion> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org On Tue, 2005-04-19 at 17:10 +0800, Sebastian Nowozin wrote: > Hello everybody, > > (please quote my email address on a reply to this email, I am not member > of the list, thanks.) > > I have wondered wether the code conversion ability of qemu could be > utilized to convert ELF .o object files compiled for i386 Linux by GCC > to .o object files for ARM/Linux. Is this possible or has something > been attempted in this direction? > > The need for such conversion occurs when porting the Java MIDP to ARM. > Due to export restrictions, for some cryptography code in the MIDP, only > linkable object files for i386 are available with the sources. (Half a > dozen small object files, clearly named like MD2.o MD5.o SHA1.o, ...). Wouldn't it be easier to write your own crypto functions conform to the API used by the platform? All the algorithms you mention above are well documented. Sincerely, Bob Deblier