All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergey Smolov <smolov@ispras.ru>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] QEMU+Aarch64: in_asm log skips instructions of loop-programs
Date: Wed, 2 Sep 2015 16:55:59 +0400	[thread overview]
Message-ID: <55E6F1DF.1090807@ispras.ru> (raw)

Hello, List!

I've found that while running Aarch64 assembler programs on QEMU with 
"-d in_asm" option enabled I receive not complete logs. For example, on 
the following assembler program which contains a loop :

[assembler]
.globl _start
bl _start
_start:
label1:
   movz  x0, 10
   subs x0, x0, 1
   b.eq label2
   b label1
label2:
hlt #57005
[/assembler]

I receive the following log which does not include "loop unrolling":
[log]
----------------
IN:
0x0000000000000000:  94000001      bl #+0x4 (addr 0x4)

----------------
IN:
0x0000000000000004:  d2800140      mov x0, #0xa

----------------
IN:
0x0000000000000008:  f1000400      subs x0, x0, #0x1 (1)

----------------
IN:
0x000000000000000c:  54000040      b.eq #+0x8 (addr 0x14)

----------------
IN:
0x0000000000000010:  17fffffd      b #-0xc (addr 0x4)


[/log]

It seems that QEMU skips some internal instructions when generates 
"in_asm" log. How to eliminate this?

Thanks in advance!

Sincerely yours,
Sergey Smolov

             reply	other threads:[~2015-09-02 13:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-02 12:55 Sergey Smolov [this message]
2015-09-02 13:50 ` [Qemu-devel] QEMU+Aarch64: in_asm log skips instructions of loop-programs Sergey Smolov
2015-09-02 16:39   ` Peter Maydell
2015-09-03  5:27     ` Sergey Smolov
2015-09-03  6:33       ` Peter Maydell
2015-09-03  7:09         ` Sergey Smolov
2015-09-03 14:28         ` Richard Henderson
     [not found] <7cd03581b882e28ef904a35a4ce1e374@ispras.ru>
2015-09-03 14:31 ` [Qemu-devel] Fwd: " Sergey Smolov
2015-09-03 15:35   ` [Qemu-devel] " Peter Maydell
2015-09-04  6:37     ` Sergey Smolov
2015-09-04 16:38       ` Sergey Smolov
2015-09-17 22:02         ` Christopher Covington
2015-09-18  8:15           ` Sergey Smolov
2015-09-18 14:26             ` Christopher Covington
2015-11-03 12:15               ` Sergey Smolov

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=55E6F1DF.1090807@ispras.ru \
    --to=smolov@ispras.ru \
    --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.