From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1GeYYj-0004zP-JX for qemu-devel@nongnu.org; Mon, 30 Oct 2006 09:56:17 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1GeYYf-0004xd-SW for qemu-devel@nongnu.org; Mon, 30 Oct 2006 09:56:17 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GeYYf-0004xT-Fv for qemu-devel@nongnu.org; Mon, 30 Oct 2006 09:56:13 -0500 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 1GeYYf-0001Sj-88 for qemu-devel@nongnu.org; Mon, 30 Oct 2006 09:56:13 -0500 From: Paul Brook Subject: Re: [Qemu-devel] qemu vs gcc4 Date: Mon, 30 Oct 2006 14:56:06 +0000 References: <45391B22.1050608@palmsource.com> <200610231858.32157.paul@codesourcery.com> <200610292335.54893.rob@landley.net> In-Reply-To: <200610292335.54893.rob@landley.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200610301456.07847.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: qemu-devel@nongnu.org On Monday 30 October 2006 04:35, Rob Landley wrote: > On Monday 23 October 2006 1:58 pm, Paul Brook wrote: > > > Although, all told, it would seem to me that what might be called for > > > here is a new gcc target. A gcc target specifically for generating > > > qemu code. That would just simply generate whatever qemu wanted for > > > function postamble. > > > > Better to just teach qemu how to generate code. > > In fact I've already done most of the infrastructure (and a fair amount > > of the legwork) for this. The only major missing function is code to do > > softmmu load/store ops. > > https://nowt.dyndns.org/ > > So given that one of the reasons for doing this would be getting away from > depending on specific and increasily out of date versions of gcc to build > the thing, what would be involved in getting this version to build under > gcc-4.x? Should work pretty much out the box. Obviously if you build anything other than m68k then all bets are off. Paul