From: Vince Weaver <vince@csl.cornell.edu>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] new qemu-linux-user multi-architecture test case
Date: Thu, 13 Aug 2009 17:45:28 -0400 (EDT) [thread overview]
Message-ID: <20090813173744.L44281@stanley.csl.cornell.edu> (raw)
Hello
I'm not sure how much interest there is in this, but I have a long-running
project where I've hand-optmized the same program for size in assembly
language for 21 different architectures.
13 of those architectures can be run by qemu-linux-user.
So if you download the package here:
http://www.deater.net/weave/vmwprod/asm/ll/ll_binaries-0.38.tar.gz
Unpack it, enter the "qemu_test" directory, modify the test_qemu.sh
script to point to your local copy of qemu, then run the script.
This can act as a quick sanity check that the various qemu-linux-user
architectures are all working.
Some issues:
+ Alpha is currently broken until the extlh patch I sent earlier
is applied
+ m68k is currently broken, a lot of necessary instructions are missing
+ crisv32 has issues with my toolchain, it errors out due to an mmap
issue during elf load. If that is commented out in qemu, it runs fine
The homepage of the project is:
http://www.deater.net/weave/vmwprod/asm/ll/ll.html
Vince
reply other threads:[~2009-08-13 21:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20090813173744.L44281@stanley.csl.cornell.edu \
--to=vince@csl.cornell.edu \
--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).