From: Laurent Desnogues <laurent.desnogues@gmail.com>
To: Chad <chad.page@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Performance bug in tcg/i386 output:
Date: Sun, 8 Nov 2009 18:56:15 +0100 [thread overview]
Message-ID: <761ea48b0911080956xebc2320yeecc96d1b439c0ed@mail.gmail.com> (raw)
In-Reply-To: <f784f5260911080947s732fa25bj1251778a7d91447f@mail.gmail.com>
On Sun, Nov 8, 2009 at 6:47 PM, Chad <chad.page@gmail.com> wrote:
> Running qemu[-i386] with -d out_asm and looking at qemu.out shows this
> test/j**/jmp pattern repeatedly:
>
> 0xb1aa40f6: test %ecx,%ecx
> 0xb1aa40f8: jne 0xb1aa4115
> 0xb1aa40fe: jmp 0xb1aa4103
> 0xb1aa4103: mov $0xc0bf,%eax
>
> Therefore there's a bug in the tcg generator creating many unnecessary
> jmps. It might get optimized out by the CPU, but it might not and it bloats
> the asm output in any case...
Some of these jumps are patched later when the target
block is translated (block chaining).
If you want to see the real output, you'll have to disassemble
after execution.
Laurent
prev parent reply other threads:[~2009-11-08 17:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-08 17:47 [Qemu-devel] Performance bug in tcg/i386 output: Chad
2009-11-08 17:56 ` Laurent Desnogues [this message]
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=761ea48b0911080956xebc2320yeecc96d1b439c0ed@mail.gmail.com \
--to=laurent.desnogues@gmail.com \
--cc=chad.page@gmail.com \
--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).