From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20) id 19hbZJ-0005Be-1o for qemu-devel@nongnu.org; Tue, 29 Jul 2003 16:59:37 -0400 Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20) id 19hbYR-00054q-Um for qemu-devel@nongnu.org; Tue, 29 Jul 2003 16:58:44 -0400 Received: from smtp4.wanadoo.fr ([193.252.22.26] helo=mwinf0504.wanadoo.fr) by monty-python.gnu.org with esmtp (Exim 4.20) id 19hbXN-0004HW-IB for qemu-devel@nongnu.org; Tue, 29 Jul 2003 16:57:37 -0400 Received: from free.fr (ATuileries-112-1-4-224.w81-53.abo.wanadoo.fr [81.53.133.224]) by mwinf0504.wanadoo.fr (SMTP Server) with ESMTP id 5267C100036E for ; Tue, 29 Jul 2003 22:57:36 +0200 (CEST) Message-ID: <3F26DFAA.2000508@free.fr> Date: Tue, 29 Jul 2003 22:57:14 +0200 From: Fabrice Bellard MIME-Version: 1.0 Subject: Re: [Qemu-devel] powerpc (debian/sid) woes References: <3F258305.3000303@petig-baender.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Reply-To: qemu-devel@nongnu.org List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org The problem is that I don't have access to a gcc-3.3 powerpc based system... Fabrice. Christof Petig wrote: > Hi, > > Since 0.1.6 I encountered occasional compile/link failures and various > errors on powerpc. Since I thought them to be temporary I did not spend > much thought about it and waited for a new (and working version). But > looking more closely these problems seem to persist ... > > Intermediate problems: > since 2003-5-27 18:50: dyngen: could not find .sdata section > > but since 2003-5-30 18:50 (and up to current CVS): > The process loops forever (gcc-3.3,-O2) or encounters an illegal > instruction (gcc-3.3, -O0). > > Since debian shipped more actual kernel headers with glibc, I am no more > able to try gcc-2.95 (gcc-3.2 fails like gcc-3.3): > > syscall.c: In function `_llseek': > syscall.c:95: more than 10 operands in `asm' > > (looks nonsense to me) > > But in any case I would like to have 3.3 working. > > Offending code attached. > > But what is even nagging me more is the fact that I don't have a working > newer wine than the one you offer for download. I tried to download > .debs from unstable, as of 2003-4-11 it's ls worked. Since 0.1.6 it > segfaults. > > Has anybody had any recent success with powerpc, a recent wine, a recent > compiler and a recent glibc? ;-) > > Christof > > Working (0.1.6) > IN: > 0x300a9990: pushl %esp > 0x300a9991: call 0x0 > > AFTER FLAGS OPT: > 0x0000: movl_T0_ESP > 0x0001: pushl_T0 > 0x0002: movl_T0_im 0x300a9996 > 0x0003: pushl_T0 > 0x0004: jmp_im 0x300a99e8 > 0x0005: end > > OUT: [size=52] > 0x60292600: mr r24,r20 > 0x60292604: addi r9,r20,-4 > 0x60292608: stwbrx r24,r0,r9 > 0x6029260c: mr r20,r9 > 0x60292610: lis r9,12299 > 0x60292614: addi r24,r9,-26218 > 0x60292618: addi r9,r20,-4 > 0x6029261c: stwbrx r24,r0,r9 > 0x60292620: mr r20,r9 > 0x60292624: lis r9,12299 > 0x60292628: addi r9,r9,-26136 > 0x6029262c: stw r9,32(r27) > 0x60292630: blr > > Failing (current CVS): > AFTER FLAGS OPT: > 0x0000: movl_T0_ESP > 0x0001: pushl_T0 > 0x0002: movl_T0_im 0x300a9996 > 0x0003: pushl_T0 > 0x0004: jmp_tb_next 0x601958f0 0x300a99e8 > 0x0005: end > > OUT: [size=64] > 0x603358f0: mr r24,r20 > 0x603358f4: addi r9,r20,-4 > 0x603358f8: stwbrx r24,r0,r9 > 0x603358fc: mr r20,r9 > 0x60335900: lis r9,12299 > 0x60335904: addi r24,r9,-26218 > 0x60335908: addi r9,r20,-4 > 0x6033590c: stwbrx r24,r0,r9 > 0x60335910: mr r20,r9 > 0x60335914: b 6045EEDC <<< strange? > 0x60335918: lis r11,24601 > 0x6033591c: lis r9,12299 > 0x60335920: addi r24,r11,22768 > 0x60335924: addi r9,r9,-26136 > 0x60335928: stw r9,32(r27) > 0x6033592c: blr > > > > > _______________________________________________ > Qemu-devel mailing list > Qemu-devel@nongnu.org > http://mail.nongnu.org/mailman/listinfo/qemu-devel > > -- Fabrice.