From: Christof Petig <christof@petig-baender.de>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] powerpc (debian/sid) woes
Date: Mon, 28 Jul 2003 22:09:41 +0200 [thread overview]
Message-ID: <3F258305.3000303@petig-baender.de> (raw)
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
next reply other threads:[~2003-07-29 7:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-28 20:09 Christof Petig [this message]
2003-07-29 20:57 ` [Qemu-devel] powerpc (debian/sid) woes Fabrice Bellard
2003-07-29 21:33 ` Jocelyn Mayer
2003-07-30 14:27 ` Jocelyn Mayer
2003-08-05 11:18 ` Christof Petig
2003-08-05 12:26 ` Herbert Pötzl
2003-08-05 13:40 ` Jocelyn Mayer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3F258305.3000303@petig-baender.de \
--to=christof@petig-baender.de \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.