From: Alexander Graf <agraf@suse.de>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Patch Tracking" <patches@linaro.org>,
"Stefan Weil" <sw@weilnetz.de>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Blue Swirl" <blauwirbel@gmail.com>,
"Claudio Fontana" <claudio.fontana@linaro.org>,
"Aurélien Jarno" <aurelien@aurel32.net>,
"Anthony Liguori" <aliguori@amazon.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>,
"Christoffer Dall" <christoffer.dall@linaro.org>,
"Richard Henderson" <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH 0/4] disas: add libvixl to support A64 disassembly
Date: Wed, 08 Jan 2014 17:19:49 +0100 [thread overview]
Message-ID: <52CD7AA5.3070106@suse.de> (raw)
In-Reply-To: <CAFEAcA_50pSCEbd3u_4zpZp5F3P0ybGAOXzpQ75rZDdVk3wiGA@mail.gmail.com>
On 01/08/2014 04:31 PM, Peter Maydell wrote:
> On 8 January 2014 14:51, Alex Bennée <alex.bennee@linaro.org> wrote:
>> Is there an argument for making this an optional component. It would be
>> useful to know how many users care about having access to the target
>> assembly. Certainly I'm only looking at it while developing TCG code.
> If you really don't want the dep you can configure with '--cxx=', and then
> we'll fall back to "no C++ compiler, don't build C++-only bits".
>
> One of my aims here is that I don't particularly want the A64
> translator to be a second class citizen in terms of what features
> it supports. Debug logs are generally useful (which is why they're
> present) and being able to have end users grab a debug log is
> nice for tracking down issues sometimes.
It's also very useful to just be able to do "x /i $pc" on the qemu
monitor. So yes, a working disassembler is defintiely a must have.
Alex
next prev parent reply other threads:[~2014-01-08 16:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-07 16:51 [Qemu-devel] [PATCH 0/4] disas: add libvixl to support A64 disassembly Peter Maydell
2014-01-07 16:51 ` [Qemu-devel] [PATCH 1/4] rules.mak: Support .cc as a C++ source file suffix Peter Maydell
2014-01-07 16:51 ` [Qemu-devel] [PATCH 2/4] rules.mak: Link with C++ if we have a C++ compiler Peter Maydell
2014-01-07 16:51 ` [Qemu-devel] [PATCH 3/4] disas: add libvixl source code for AArch64 A64 disassembler Peter Maydell
2014-01-07 16:51 ` [Qemu-devel] [PATCH 4/4] disas: Implement disassembly output for A64 Peter Maydell
2014-01-07 22:30 ` [Qemu-devel] [PATCH 0/4] disas: add libvixl to support A64 disassembly Stefan Weil
2014-01-07 23:00 ` Peter Maydell
2014-01-08 6:55 ` Stefan Weil
2014-01-08 10:07 ` Peter Maydell
2014-01-07 22:53 ` Stefan Weil
2014-01-08 14:51 ` Alex Bennée
2014-01-08 15:31 ` Peter Maydell
2014-01-08 16:19 ` Alexander Graf [this message]
2014-01-07 23:46 ` Peter Maydell
2014-01-08 14:48 ` Alex Bennée
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=52CD7AA5.3070106@suse.de \
--to=agraf@suse.de \
--cc=alex.bennee@linaro.org \
--cc=aliguori@amazon.com \
--cc=aurelien@aurel32.net \
--cc=blauwirbel@gmail.com \
--cc=christoffer.dall@linaro.org \
--cc=claudio.fontana@linaro.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=patches@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=sw@weilnetz.de \
/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).