From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:43217)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <rob@landley.net>) id 1VLFOH-0007kf-Ft
	for qemu-devel@nongnu.org; Sun, 15 Sep 2013 12:41:48 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <rob@landley.net>) id 1VLFOA-0007xF-6b
	for qemu-devel@nongnu.org; Sun, 15 Sep 2013 12:41:41 -0400
Received: from mail-ye0-f177.google.com ([209.85.213.177]:36709)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <rob@landley.net>) id 1VLFOA-0007x9-2O
	for qemu-devel@nongnu.org; Sun, 15 Sep 2013 12:41:34 -0400
Received: by mail-ye0-f177.google.com with SMTP id q9so1264981yen.8
	for <qemu-devel@nongnu.org>; Sun, 15 Sep 2013 09:41:32 -0700 (PDT)
Date: Sun, 15 Sep 2013 11:41:30 -0500
From: Rob Landley <rob@landley.net>
References: <52306808.4030701@huawei.com>
In-Reply-To: <52306808.4030701@huawei.com> (from claudio.fontana@huawei.com
	on Wed Sep 11 07:54:32 2013)
Message-Id: <1379263290.1974.26@driftwood>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; DelSp=Yes; Format=Flowed
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Subject: Re: [Qemu-devel] [RFC 0/4] ARM aarch64 disas output libvixl support
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Claudio Fontana <claudio.fontana@huawei.com>
Cc: Peter Maydell <peter.maydell@linaro.org>, "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>

On 09/11/2013 07:54:32 AM, Claudio Fontana wrote:
>=20
> This is the aarch64 libvixl support patchset in the current state.
> It provides (limited) support for disassembly output on aarch64.
> Only host disassembly is enabled, since target for aarch64 is not in =20
> yet.
>=20
> An external objdump solution as exemplified before by R.H. seems =20
> preferable
> to me, even if it means giving up the monitor support.
> I'd rather have correct output from -d.
> The run time need for debugging assembly is already fulfilled by gdb =20
> better
> than the monitor.
>=20
> libvixl does not support many opcodes right now, is C++, and it is =20
> documented
> as working only for a 64bit host with a LP64 memory model.

Wait, incorporating C++ code into qemu was considered the _good_ =20
solution?

What was the bad solution?

Rob=