All of lore.kernel.org
 help / color / mirror / Atom feed
From: " Torbjörn Andersson" <tobbe.tt@home.se>
To: qemu-devel  <qemu-devel@nongnu.org>
Subject: Re: Re: SV: [Qemu-devel] ARM CPSR and conditional instructions
Date: Thu, 23 Nov 2006 08:05:53 +0000	[thread overview]
Message-ID: <80846442723677@lycos-europe.com> (raw)

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

We are currently debugging the situation and we are actually not sure about the real reason for our current situation.

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.

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.

/Torbjörn

> Från: Wolfgang Schildbach <Wolfgang.Schildbach@codingtechnologies.com>
> Till: qemu-devel@nongnu.org
> Rubrik: Re: SV: [Qemu-devel] ARM CPSR and conditional instructions
> Datum: Thu, 23 Nov 2006 08:43:50 +0100

> I very much doubt there is any problem with the CPSR. The ARM emulation 
> has correctly run hundreds of millions of instructions coming from many 
> different compilers and hand-written assembly. Can you be more precise in 
> what the effect is that you see?
> 
> - Wolfgang
> 
> qemu-devel-bounces+wolfgang.schildbach=codingtechnologies.com@nongnu.org 
> wrote on 22.11.2006 22:13:01:
> 
> > 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
> >  _______________________________________________
> > Qemu-devel mailing list
> > Qemu-devel@nongnu.org
> > <a
> href=http://lists.nongnu.org/mailman/listinfo/qemu-devel>http://listsnongnu
> .org/mailman/listinfo/qemu-devel</a>
> 
> 
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> <a
> href=http://lists.nongnu.org/mailman/listinfo/qemu-devel>http://listsnongnu
> .org/mailman/listinfo/qemu-devel</a>


Kärlek och hur mycket pengar? Få svar idag om din morgondag! http://horoskop.spray.se/

             reply	other threads:[~2006-11-23  8:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-23  8:05  Torbjörn Andersson [this message]
2006-11-23 15:28 ` SV: [Qemu-devel] ARM CPSR and conditional instructions 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=80846442723677@lycos-europe.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.