From: "Torbjörn Andersson" <tobbe.tt@home.se>
To: qemu-devel@nongnu.org
Subject: SV: [Qemu-devel] ARM CPSR and conditional instructions
Date: Wed, 22 Nov 2006 22:13:01 +0100 [thread overview]
Message-ID: <004801c70e7a$fe63a290$3101a8c0@ttlaptop> (raw)
In-Reply-To: <000601c70db2$4bead750$3101a8c0@ttlaptop>
[-- Attachment #1: Type: text/plain, Size: 1422 bytes --]
I’m sorry for spamming you mailing list with my duplicate posts. I had some
problems sending my mail.
/Torbjörn
_____
Från: qemu-devel-bounces+tobbe.tt_home.se=spray.se@nongnu.org
[mailto:qemu-devel-bounces+tobbe.tt_home.se=spray.se@nongnu.org] För
Torbjörn Andersson
Skickat: den 21 november 2006 22:16
Till: qemu-devel@nongnu.org
Ämne: [Qemu-devel] ARM CPSR and conditional instructions
Hello qemu developers!
I´m using QEMU for some ARM debugging and I have som questions regardning
the CPSR register. I get the feeling that the CPSR condition code bits,
representing the results from the ALU, are not maintained at all points. Is
the JIT in QEMU tailored in any way towards GCC output? (Resulting in issues
with the output of other compilers that make use of the conditional
execution of instructions etc.)
What I want to do is to try to verify QEMU maintains the CPSR register and
if not fix it. However, it is not trivial identify where the updates should
be placed. The relationship between translate.c and op.c is not trival I
must say :)
I would be happy I anyone here could give me some pointers on how the
updates of the CPSR register is done today and what the strategy is. I guess
there are plenty of performance ideas here as in the rest of qemu.
Does anyone have any reflection on this topic or can anyone give me some
pointers?
Torbjörn
[-- Attachment #2: Type: text/html, Size: 5284 bytes --]
next prev parent reply other threads:[~2006-11-23 0:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-21 21:16 [Qemu-devel] ARM CPSR and conditional instructions Torbjörn Andersson
2006-11-22 21:13 ` Torbjörn Andersson [this message]
2006-11-23 7:43 ` SV: " Wolfgang Schildbach
2006-11-23 18:22 ` Justin Fletcher
-- strict thread matches above, loose matches on Subject: below --
2006-11-23 8:05 Torbjörn Andersson
2006-11-23 15:28 ` Paul Brook
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='004801c70e7a$fe63a290$3101a8c0@ttlaptop' \
--to=tobbe.tt@home.se \
--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).