From: Lauro Ramos Venancio <lauro.venancio@indt.org.br>
To: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] qemu-arm: wrong execution of post-indexed loads when Rm and Rd are the same register
Date: Thu, 15 Mar 2007 16:35:24 -0300 [thread overview]
Message-ID: <1173987324.9939.0.camel@edgy-laptop> (raw)
Qemu-arm is wrongly executing post-indexed loads when Rm and Rd are
the same register. For example:
ldr r0, [r1], +r0
Current behavior:
r0 <- [r1]
r1 <- r1 + r0
Expected behavior:
addr <- r1
r1 <- r1 + r0
r0 <- [addr]
The attached patch fixes this bug. Patched by me and Rodrigo Vivi.
This patch was made based on qemu 0.9.
Lauro Venancio
next reply other threads:[~2007-03-15 19:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-15 19:35 Lauro Ramos Venancio [this message]
2007-03-15 19:43 ` [Qemu-devel] Re: qemu-arm: wrong execution of post-indexed loads when Rm and Rd are the same register Lauro Ramos Venancio
2007-03-15 20:03 ` [Qemu-devel] " Paul Brook
2007-03-15 20:32 ` Rodrigo Vivi
2007-03-15 21:10 ` Paul Brook
2007-03-15 21:19 ` Rodrigo Vivi
2007-03-15 21:55 ` Laurent Desnogues
2007-03-15 22:04 ` Paul Brook
2007-03-16 20:42 ` Lauro Ramos Venancio
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=1173987324.9939.0.camel@edgy-laptop \
--to=lauro.venancio@indt.org.br \
--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).