From: Aurelien Jarno <aurelien@aurel32.net>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: riku voipio <riku.voipio@iki.fi>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] arm-dis: Include opcode hex when doing disassembly
Date: Wed, 12 Jan 2011 15:13:54 +0100 [thread overview]
Message-ID: <20110112141354.GA7701@hall.aurel32.net> (raw)
In-Reply-To: <AANLkTim5_ZpUiSiPvdzVrmGhfNxFqXDt2HhXCnve0uLz@mail.gmail.com>
On Mon, Jan 10, 2011 at 11:09:28AM -0600, Peter Maydell wrote:
> On 10 January 2011 10:49, Aurelien Jarno <aurelien@aurel32.net> wrote:
> > Strangely on arm host, the opcode hex is already included, as shown
> > below:
> >
> > | OUT: [size=308]
> > | 0x01001ec0: e5974004 ldr r4, [r7, #4]
> > | 0x01001ec4: e1a04804 lsl r4, r4, #16
> > | 0x01001ec8: e1a04824 lsr r4, r4, #16
> > | 0x01001ecc: e1a04404 lsl r4, r4, #8
> >
> > Maybe there is just an option to enable to allow that?
>
> It looks like that's just an ugly #ifdef in disas.c:disas():
> #ifdef __arm__
> /* since data is included in the code, it is better to
> display code data too */
> fprintf(out, "%08x ", (int)bfd_getl32((const bfd_byte *)pc));
> #endif
>
> ...so I guess if we commit the patch I submitted we should
> just delete that #ifdef.
>
I have applied this patch, and committed another one that removes this
hack.
--
Aurelien Jarno GPG: 1024D/F1BCDB73
aurelien@aurel32.net http://www.aurel32.net
prev parent reply other threads:[~2011-01-12 14:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-10 16:16 [Qemu-devel] [PATCH] arm-dis: Include opcode hex when doing disassembly Peter Maydell
2011-01-10 16:49 ` Aurelien Jarno
2011-01-10 17:09 ` Peter Maydell
2011-01-10 17:31 ` Aurelien Jarno
2011-01-12 14:13 ` Aurelien Jarno [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=20110112141354.GA7701@hall.aurel32.net \
--to=aurelien@aurel32.net \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=riku.voipio@iki.fi \
/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).