From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1DUxh1-00062o-HT for qemu-devel@nongnu.org; Sun, 08 May 2005 22:08:24 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1DUxgr-0005xF-Co for qemu-devel@nongnu.org; Sun, 08 May 2005 22:08:18 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DUxgp-0005r4-4x for qemu-devel@nongnu.org; Sun, 08 May 2005 22:08:11 -0400 Received: from [62.89.75.144] (helo=bozon2.softax.com.pl) by monty-python.gnu.org with esmtp (TLS-1.0:DHE_RSA_3DES_EDE_CBC_SHA:24) (Exim 4.34) id 1DUxTm-0005ng-DM for qemu-devel@nongnu.org; Sun, 08 May 2005 21:54:42 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by bozon2.softax.com.pl (Postfix) with ESMTP id BB05FDC32B for ; Mon, 9 May 2005 03:48:37 +0200 (CEST) Received: from bozon2.softax.com.pl ([127.0.0.1]) by localhost (bozon2.softax.pl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 12363-20 for ; Mon, 9 May 2005 03:48:34 +0200 (CEST) Received: from zdzicha.k.local (dli52.neoplus.adsl.tpnet.pl [83.24.38.52]) by bozon2.softax.com.pl (Postfix) with ESMTP id 5346EDC326 for ; Mon, 9 May 2005 03:48:34 +0200 (CEST) Content-Type: text/plain; charset="iso-8859-1" From: Sebastian Kaliszewski Subject: Re: [Qemu-devel] Stupid (probably) idea wrt dyngen & gcc 3.4 & 4.0 Date: Mon, 9 May 2005 03:55:24 +0200 References: <200505090202.00547.sk@z.pl> <200505090140.57249.paul@nowt.org> In-Reply-To: <200505090140.57249.paul@nowt.org> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200505090355.24247.sk@z.pl> Reply-To: sk@z.pl, 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 So the idea was indeed stupid :) On Monday 09 May 2005 02:40, Paul Brook wrote: > No. The main problem with gcc3.4 was that we weren't using FORCE_RET > everywhere that we should. This has mostly been fixed now. I see... [snip] > > I've got a solution for x86/x86-64 that's 95% complete, using the metho= d > I suggested in a previous email.=20 So, since ret is too small to be replaced with jump, you relocate the blo= ck=20 following ret few bytes further, and retarget all relevant jumps? > I hope to be submitting a patch shortly. > I expect most other hosts (particularly the RISC based ones) to be much > simpler to fix. Nice. rgds Sebastian Kaliszewski