From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1GcWgF-0003Re-Nk for qemu-devel@nongnu.org; Tue, 24 Oct 2006 20:31:39 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1GcWgD-0003Qg-H0 for qemu-devel@nongnu.org; Tue, 24 Oct 2006 20:31:38 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GcWgD-0003QS-3r for qemu-devel@nongnu.org; Tue, 24 Oct 2006 20:31:37 -0400 Received: from [65.74.133.4] (helo=mail.codesourcery.com) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1GcWgC-00065t-KG for qemu-devel@nongnu.org; Tue, 24 Oct 2006 20:31:36 -0400 From: Paul Brook Subject: Re: [Qemu-devel] qemu vs gcc4 Date: Wed, 25 Oct 2006 01:24:48 +0100 References: <45391B22.1050608@palmsource.com> <200610231937.44676.paul@codesourcery.com> <200610241939.06772.rob@landley.net> In-Reply-To: <200610241939.06772.rob@landley.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200610250124.50202.paul@codesourcery.com> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Rob Landley Cc: qemu-devel@nongnu.org On Wednesday 25 October 2006 00:39, Rob Landley wrote: > On Monday 23 October 2006 2:37 pm, Paul Brook wrote: > > It turn out that qemu already does most of the hard work, and a code > > generation backend is fairly simple. The diff for my current > > implementation is <2k lines of common code, plus <1k lines for each of > > x86, amd64 and ppc32 hosts. > > My understanding is that the version you linked to with your new backend > currently _only_ supports coldfire/m68k? ColdFire is the only target that uses it exclusively. Arm is currently a hybrid of dyngen and the new backend. So is i386, to a lesser extent. Other targets have minimal changes necessary to make them work. > Do you have a quick "here's you how try it out" thing? (For example, when > I first show people qemu I boot a knoppix cd image under it. Fast and > shiny. :) One of my goals when writing it was to be able to reuse most of the existing qemu code. There should be no user-visible impact. Unless you already understand how qemu/dyngen works it's not going to mean a lot to you. The end result is very similar, just a slightly different strategy for getting there. In theory it should allow better performance, but that's still a way off. https://nowt.dyndns.org/ has patches against cvs (thought they may be slightly out of date), and a complete svn repository you can checkout. Build it just like normal qemu. Paul