From: "Hervé Poussineau" <hpoussin@reactos.org>
To: etou.zh@gmail.com
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: [Qemu-devel] r4k doesn't support movz
Date: Fri, 18 May 2012 21:52:06 +0200 [thread overview]
Message-ID: <4FB6A866.5030504@reactos.org> (raw)
Hi,
Zhi-zhou Zhang a écrit :
> I found that when qemu-system-mips64el executed 'movz' with -M mips,
> it would raise a reserved instruction exception.
> The mips spec describes movz as below:
>
> Mnemonic Instructio Defined in MIPS ISA
> MOVZ Move Conditional on Zero MIPS32
>
> I think ISA-64 should support MIPS32 instructions for compatible. am I
> right?
movz instruction is available on MIPS4 and MIPS32 instruction sets (+
Loongson2E/2F CPUs)
However, by default, 'mips' machine on qemu-system-mips64el uses a R4000
CPU, which is only MIPS3 compatible.
You need to use another cpu which is MIPS4 or MIPS32 compatible with the
-cpu option.
Regards,
Hervé
next reply other threads:[~2012-05-18 19:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-18 19:52 Hervé Poussineau [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-05-18 11:38 [Qemu-devel] r4k doesn't support movz Zhi-zhou Zhang
2012-05-19 1:02 ` Johnson, Eric
2012-05-19 2:30 ` Jia Liu
2012-05-19 9:02 ` Aurelien Jarno
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=4FB6A866.5030504@reactos.org \
--to=hpoussin@reactos.org \
--cc=etou.zh@gmail.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).