From: Simon Willcocks <simon.willcocks@t-online.de>
To: qemu-devel@nongnu.org
Cc: paul@codesourcery.com
Subject: Re: [Qemu-devel] [PATCH] ARM CPSR and conditional instructions - revisited
Date: Sun, 16 Nov 2008 02:25:45 +0100 [thread overview]
Message-ID: <d5bde3fe4f.simonwillcocks@home.invalid> (raw)
In-Reply-To: <200811141248.31086.paul@codesourcery.com>
In message <200811141248.31086.paul@codesourcery.com>
Paul Brook <paul@codesourcery.com> wrote:
> On Friday 14 November 2008, Simon Willcocks wrote:
> > Hello,
> >
> > I was having a problem emulating some ARM code
>
> You need to use a newer qemu. This has been fixed for ages.
You're right; on the 1st April, I guess that makes me an April Fool :-)
On the other hand, it has raised a couple of questions.
1. At what point will there be a new release of the software?
Is there a target being worked towards?
2. How do I compile my simple test program?
This used to be good enough:
gcc flags_test1.c -o flags_test1 qemu-0.9.1/arm-linux-user/libqemu.a \
-I qemu-0.9.1 -DNEED_CPU_H -Iqemu-0.9.1/fpu -I qemu-0.9.1/arm-linux-user/ \
-Wall qemu-0.9.1/osdep.c -I qemu-0.9.1/target-arm/ -D_XOPEN_SOURCE=600
But now libqemu.a seems to need a lot of features from other places that I
can't easily identify. (Just osdep.c covered everything, before.)
I can understand the emulator needing wrapped malloc-like routines, but why
does the base emulator (which is what I thought the libqemu.a file
contained) need to know about mmap_lock?
I'm a little frustrated, and inclined to go back to using the 0.9.1. library
with my patch to continue, although there are presumably other improvements
to the development build.
Thanks,
Simon
--
ROLF - The RISC OS Look and Feel on Linux.
http://stoppers.drobe.co.uk
http://ro-lookandfeel.blogspot.com/
next prev parent reply other threads:[~2008-11-16 1:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-14 9:52 [Qemu-devel] [PATCH] ARM CPSR and conditional instructions - revisited Simon Willcocks
2008-11-14 12:48 ` Paul Brook
2008-11-16 1:25 ` Simon Willcocks [this message]
2008-11-16 16:49 ` Paul Brook
2008-11-16 21:34 ` Simon Willcocks
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=d5bde3fe4f.simonwillcocks@home.invalid \
--to=simon.willcocks@t-online.de \
--cc=paul@codesourcery.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 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.