From mint-bounce@lists.fishpool.fi Thu Apr 30 10:29:33 2009 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=9Nt0u9RKama4At6arEahRAt1FRjlfLinKIyqOToyJ74=; b=Rg0NLZH43YvUFzHHo3exHkkscf672wH9RQ5riDlDwXIKd1opdZYTJebgMqnGdwZRB5 HeYwVssM1ZbeBhl+23VrODftYdG8Fn0xOO+m0DWXCN8iobHgQ3ec3BzwZ8J/0vPFzcf3 wYNHxrtvYhbuGOtyXX2l4d84uCrXt5iSEhsys= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; b=AVbOoj0ARmYW/5vjvpLXh3FXdkXyvbt5TMUf9OitvqD/Z6IgSxva7hEGBnJixBYWgX jj2a7VhPkHouy2CtU/Sp1JZrpAkNUsTeGRFs9r9CbUCDWcgjynt9bSwFZf9IKPDbD6N+ dWpWx5+8Gd/5xFMOWxIFugez3fcvL09yvWObY= Message-ID: <49F9B4BE.7050502@freesbee.fr> Date: Thu, 30 Apr 2009 16:25:02 +0200 From: =?ISO-8859-1?Q?Vincent_Rivi=E8re?= User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) MIME-Version: 1.0 To: mint@lists.fishpool.fi Subject: Re: [MiNT] MiNTLib for ColdFire References: <49F743B1.8030803@freesbee.fr> <1240957935.9590.38.camel@joy> <49F78A7A.9020001@freesbee.fr> <1240985088.4402.13.camel@petr> <49F803C5.9050303@freesbee.fr> <20090430144731.upgjp2o4080o8kc8@pop.freeola.net> In-Reply-To: <20090430144731.upgjp2o4080o8kc8@pop.freeola.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: vincent.riviere@freesbee.fr Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: p.slegg@scubadivers.co.uk a écrit : > 2. M68k assembler to Cf issues. Could existing assembler apps be > de-compiled > into C (on any platform) so that they could be ported to Cf or any other > OS/hardware ? I realise de-compiling isn't great but I gather it's a lot > better than it used to be. TOS executables can't be decompiled reliably. Most parts can be disassembled to assembler sources. In clean executables, the CPU instructions are located only in the TEXT segment. Unfortunately, constant data is also mixed with instructions in the TEXT segment. So when a disassembler works on it, it can't know if the bytes are CPU instructions (needing to be disassembled) or data (needing to be converted into data declarations). However, the disassembling process could be assisted by a human to choose how the bytes should be treated. Then decompilation of assembler sources to C would be very, very difficult, if not impossible. Hand-written assembler sources could probably never be decompiled to C sources, because they usually have different structures. Some assembler code generated by very old and bad C compilers (like some parts of the TOS ROMs) is easily recognizable, it always has the same structure, so it is a good candidate for trying decompilation. But I'm pretty sure it would not produce useful results. I hope to be wrong. -- Vincent Rivière