From: Vince Weaver <vince@csl.cornell.edu>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] mipsIV support for mips-linux-user
Date: Sun, 29 Mar 2009 16:56:35 -0400 (EDT) [thread overview]
Message-ID: <20090329165112.G16354@stanley.csl.cornell.edu> (raw)
Hello
I have some 32-bit mips binaries compiled with -mips4 -O3.
These run fine on an actual mips r12k system I have, but
fail with default mips-linux-user (0.10.1).
This is because by default mips-linux-user does not have support enabled
for mipsIV instructions. This is because MIPS_HFLAG_COP1X
is not enabled on any of the cpus supported by mips-linux-user.
So my question, what is the correct way to fix this? Add a R4000 class
CPU that can be seen with mips-linux-user? Or should the default for
user operation just enable this because it supports more binaries?
Vince
next reply other threads:[~2009-03-29 20:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-29 20:56 Vince Weaver [this message]
2009-03-30 1:05 ` [Qemu-devel] mipsIV support for mips-linux-user Aurelien Jarno
2009-03-30 2:14 ` Vince Weaver
2009-03-30 4:35 ` Aurelien Jarno
2009-03-30 17:29 ` Vince Weaver
2009-04-08 22:17 ` Aurelien Jarno
2009-04-09 1:00 ` Vince Weaver
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=20090329165112.G16354@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).