From: Jocelyn Mayer <l_indien@magic.fr>
To: Karel Gardas <kgardas@objectsecurity.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Problem with PPC user emulation.
Date: 14 May 2004 21:42:06 +0200 [thread overview]
Message-ID: <1084563725.1626.7912.camel@jma1.dev.netgem.com> (raw)
In-Reply-To: <Pine.LNX.4.43.0405142122060.28976-100000@thinkpad.gardas.net>
On Fri, 2004-05-14 at 21:26, Karel Gardas wrote:
> On Fri, 14 May 2004, Jocelyn Mayer wrote:
>
> > On Fri, 2004-05-14 at 19:59, Karel Gardas wrote:
> > > Hello,
> > >
> > > I've tried PPC user emulation provided by this week source tree, but w/o
> > > success. I've tested crosstool's 4 test binaries (hello world in c/c++
> > > static and dynamic) but all four crash with:
> > >
> > > thinkpad:/mnt/karel/cross-gcc/result/powerpc-405-linux-gnu/gcc-3.4.0-glibc-2.3.2/tmp$ ppc.sh ./powerpc-405-linux-gnu-hello
> > > *** ERROR: idx a0 already assigned to a direct opcode
> > > *** ERROR: unable to join indirect table idx [a0-37]
> > > *** ERROR initializing PPC instruction 0xa0 0x37 0xfe
> > > /opt/qemu-scripts/bin/ppc.sh: line 3: 3496 Segmentation fault qemu-ppc -L /mnt/karel/cross-gcc/result/powerpc-405-linux-gnu/gcc-3.4.0-glibc-2.3.2/powerpc-405-linux-gnu/ $@
> > > thinkpad:/mnt/karel/cross-gcc/result/powerpc-405-linux-gnu/gcc-3.4.0-glibc-2.3.2/tmp$
> > >
> > > I used crosstool-0.28-pre13 for building ppc crosscompiler which is
> > > gcc3.4.0 and glibc2.3.2 combination.
> > >
> >
> > What is your host machine ?
>
> Debian GNU/Linux 3.0.
On a PC ?
>
> > It seems there is a mess in the way sections are handled by this gcc
> > version and/or for your host machine.
> > This seems clear to me, because there can be no instruction with this
> > opcode, as major opcode is 6 bits long in PPC and so can't be 0xa0.
> >
> > Could you please send me the qemu binary by mail, so I could check the
> > executable structure (the opcode table structure, in fact...) ?
>
> Sure! I will send you the smaller one (C statically linked hello world
> app)
Well, I need the Qemu executable, not the emulated program, because the
point you report is a bug inside qemu: it stops before trying to execute
any emulated code, and I want to study the way it's been compiled by
gcc...
> > But you may not be able to execute PPC405 dedicated binaries,
> > as this CPU implements some instructions that aren't in the PPC spec
> > then not emulated by Qemu.
>
> Aha! This might be the issue.
This is not the issue for your crash, but you may have other problems
later, using PPC405 binaries. I will had the 405 dedicated instructions
later, when the PPC core will more stable (I still have ennoying bugs to
solve).
--
Jocelyn Mayer <l_indien@magic.fr>
Never organized
next prev parent reply other threads:[~2004-05-14 19:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-14 17:59 [Qemu-devel] Problem with PPC user emulation Karel Gardas
2004-05-14 19:25 ` Jocelyn Mayer
2004-05-14 19:26 ` Karel Gardas
2004-05-14 19:42 ` Jocelyn Mayer [this message]
2004-05-14 19:44 ` Karel Gardas
2004-05-14 20:33 ` Herbert Poetzl
2004-05-14 20:42 ` Karel Gardas
2004-05-14 21:44 ` J. 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=1084563725.1626.7912.camel@jma1.dev.netgem.com \
--to=l_indien@magic.fr \
--cc=kgardas@objectsecurity.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).