From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: "Torbjörn Andersson" <tobbe.tt@home.se>
Subject: Re: SV: [Qemu-devel] ARM CPSR and conditional instructions
Date: Thu, 23 Nov 2006 15:28:59 +0000 [thread overview]
Message-ID: <200611231529.01318.paul@codesourcery.com> (raw)
In-Reply-To: <80846442723677@lycos-europe.com>
> However, we have seen that the condition bits in CPSR differers compared to
> one other arm instruction set simulator, running the same binary. This
> indicate for us that there might be something wrong i QEMU (translate.c
> op.c for ARM). However, it is not proven yet.
The only restriction it that you can't set the N and Z bits simultaneously.
This never occurs under normal circumstances, only if you directly modify the
CPSR value.
> However, our understanding for the situation would improve if the strategy
> for simulating the conditional execution of ARM instructions is understood.
>
> Is a conditional ARM instruction treated as a branch-point, an end marker
> for a TB? If not, jumps qemu within a TB?
> Is it possible to describe the strategy with a reasonable effort? I would
> be very greatfull.
A TB is terminated at a branch, and at some instructions that modify system
state (eg. moves to system registers, and the svc and bkpt instructions).
Conditional instructions do not terminate the TB unless they are conditional
branches.
Paul
next prev parent reply other threads:[~2006-11-24 23:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-23 8:05 Re: SV: [Qemu-devel] ARM CPSR and conditional instructions Torbjörn Andersson
2006-11-23 15:28 ` Paul Brook [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-11-21 21:16 Torbjörn Andersson
2006-11-22 21:13 ` SV: " Torbjörn Andersson
2006-11-23 7:43 ` Wolfgang Schildbach
2006-11-23 18:22 ` Justin Fletcher
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=200611231529.01318.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=qemu-devel@nongnu.org \
--cc=tobbe.tt@home.se \
/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).