From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Ea1U1-000325-Sq for qemu-devel@nongnu.org; Wed, 09 Nov 2005 20:44:09 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Ea1Tz-0002zz-NE for qemu-devel@nongnu.org; Wed, 09 Nov 2005 20:44:09 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ea1Tz-0002ze-4r for qemu-devel@nongnu.org; Wed, 09 Nov 2005 20:44:07 -0500 Received: from [81.29.64.88] (helo=mail.shareable.org) by monty-python.gnu.org with esmtp (TLS-1.0:DHE_RSA_3DES_EDE_CBC_SHA:24) (Exim 4.34) id 1Ea1Tz-0007ex-5P for qemu-devel@nongnu.org; Wed, 09 Nov 2005 20:44:07 -0500 Received: from mail.shareable.org (localhost [127.0.0.1]) by mail.shareable.org (8.12.8/8.12.8) with ESMTP id jAA1i4Hc031729 for ; Thu, 10 Nov 2005 01:44:04 GMT Received: (from jamie@localhost) by mail.shareable.org (8.12.8/8.12.8/Submit) id jAA1i4re031727 for qemu-devel@nongnu.org; Thu, 10 Nov 2005 01:44:04 GMT Date: Thu, 10 Nov 2005 01:44:04 +0000 From: Jamie Lokier Subject: Re: [Qemu-devel] patch for qemu with newer gcc-3.4.x (support repz retq optimization for amd processors correctly) Message-ID: <20051110014404.GC2321@mail.shareable.org> References: <43724B52.3050101@mail.ru> <200511091945.26239.paul@codesourcery.com> <4372532E.4090104@mail.ru> <200511100133.55709.jseward@acm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200511100133.55709.jseward@acm.org> 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 > > The use of gcc to generate the back end in QEMU's early days was a > clever way to get the project up and running quickly. But surely > now it would be better to transition to a handwritten backend, so It should be trivial to take the _currently_ generated GCC code for all the architectures QEMU is commonly built on, and just distribute that code with the QEMU source. Then it would be independent of future changes to GCC. I understand a handwritten backend is already being written. But until a proper one is done, wouldn't that serve as a useful stopgap? -- Jamie