qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Torbjörn Andersson" <tobbe.tt@home.se>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] ARM CPSR and conditional instructions
Date: Tue, 21 Nov 2006 20:08:34 +0100	[thread overview]
Message-ID: <000c01c70da0$71d45de0$3101a8c0@ttlaptop> (raw)

[-- Attachment #1: Type: text/plain, Size: 999 bytes --]

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: 2738 bytes --]

             reply	other threads:[~2006-11-22  1:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-21 19:08 Torbjörn Andersson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-11-21 21:16 [Qemu-devel] ARM CPSR and conditional instructions Torbjörn Andersson

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='000c01c70da0$71d45de0$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).