From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.34) id 1BPLFD-0000r4-1d for qemu-devel@nongnu.org; Sun, 16 May 2004 08:59:55 -0400 Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.34) id 1BPLCe-0008LH-QO for qemu-devel@nongnu.org; Sun, 16 May 2004 08:57:47 -0400 Received: from [194.97.50.131] (helo=mout0.freenet.de) by monty-python.gnu.org with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.34) id 1BPLCT-0008EU-Fb for qemu-devel@nongnu.org; Sun, 16 May 2004 08:57:06 -0400 Received: from [194.97.50.136] (helo=mx3.freenet.de) by mout0.freenet.de with asmtp (Exim 4.34) id 1BPLCQ-0006bD-MQ for qemu-devel@nongnu.org; Sun, 16 May 2004 14:57:02 +0200 Received: from p213.54.3.76.tisdip.tiscali.de ([213.54.3.76] helo=lfs.local) by mx3.freenet.de with asmtp (ID mbuesch@freenet.de) (Exim 4.33 #3) id 1BPLCQ-0004GH-F5 for qemu-devel@nongnu.org; Sun, 16 May 2004 14:57:02 +0200 From: Michael Buesch Date: Sun, 16 May 2004 14:56:55 +0200 MIME-Version: 1.0 Content-Disposition: inline Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Message-Id: <200405161457.01533.mbuesch@freenet.de> Subject: [Qemu-devel] qemu-0.5.5 compile regression 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 =2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, qemu-0.5.5 suffers from a gcc regression. gcc -Wall -O2 -g -fomit-frame-pointer -O2 -mpreferred-stack-boundary=3D2 -f= align-functions=3D0 -fno-reorder-blocks -fno-optimize-sibling-calls -I. -I/= home/mb/qemu-0.5.5/target-i386 -I/home/mb/qemu-0.5.5 -D_GNU_SOURCE -c -o op= =2Eo /home/mb/qemu-0.5.5/target-i386/op.c /home/mb/qemu-0.5.5/target-i386/ops_template_mem.h: In function `op_rolb_ke= rnel_T0_T1_cc': /home/mb/qemu-0.5.5/softmmu_header.h:179: error: can't find a register in c= lass `GENERAL_REGS' while reloading `asm' A workaround for the problem is compiling with -O1 I don't know how to workaround this properly. [Please CC: me on replies, as I'm not subscribed] =2D --=20 Regards Michael Buesch [ http://www.tuxsoft.de.vu ] =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAp2UcFGK1OIvVOP4RAv+tAJ9fNivZsqLzELE86gzU+8zHFE5Z3gCdE7XZ YS+P092APY0zEWa2OghAhsU=3D =3DW9Fk =2D----END PGP SIGNATURE-----