All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Richard Henderson <rth@twiddle.net>
Cc: jcmvbkbc@gmail.com, gxt@mprc.pku.edu.cn, qemu-devel@nongnu.org,
	claudio.fontana@gmail.com, proljc@gmail.com
Subject: Re: [Qemu-devel] [PATCH 0/2] Disassembly with external objdump
Date: Sat, 10 Aug 2013 10:16:27 +0100	[thread overview]
Message-ID: <CAFEAcA-KuaDVbkUZDc=phiZ7D9YeGSBHgat1+vb-7pZrVg6VkQ@mail.gmail.com> (raw)
In-Reply-To: <1376075958-21932-1-git-send-email-rth@twiddle.net>

On 9 August 2013 20:19, Richard Henderson <rth@twiddle.net> wrote:
> We have one host platform (aarch64), and three target platforms
> (openrisc, unicore32, xtensa) with no built-in disassembly support,
> thanks largely to gplv3 silliness.

FWIW, there's an aarch64 BSD disassembler available as part
of vixl: https://github.com/armvixl/vixl

but this is still going to be useful for other platforms anyway.

-- PMM

  parent reply	other threads:[~2013-08-10  9:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-09 19:19 [Qemu-devel] [PATCH 0/2] Disassembly with external objdump Richard Henderson
2013-08-09 19:19 ` [Qemu-devel] [PATCH 1/2] disas: Implement fallback to dump object code as hex Richard Henderson
2013-08-09 19:19 ` [Qemu-devel] [PATCH 2/2] disas: Add disas-objdump.pl Richard Henderson
2013-08-10  4:08   ` Max Filippov
2013-08-10 10:39     ` Richard Henderson
2013-08-10  1:54 ` [Qemu-devel] [PATCH 0/2] Disassembly with external objdump Jia Liu
2013-08-10  9:16 ` Peter Maydell [this message]
2013-08-10 10:22   ` Claudio Fontana
2013-08-10 15:45     ` Peter Maydell
2013-08-10 16:42       ` Richard Henderson
2013-08-10 16:53         ` Max Filippov
2013-08-10 19:47           ` Richard Henderson
2013-09-03 13:18             ` Claudio Fontana
2013-08-11  8:59 ` Blue Swirl

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='CAFEAcA-KuaDVbkUZDc=phiZ7D9YeGSBHgat1+vb-7pZrVg6VkQ@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=claudio.fontana@gmail.com \
    --cc=gxt@mprc.pku.edu.cn \
    --cc=jcmvbkbc@gmail.com \
    --cc=proljc@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    /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.