All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Lucien Murray-Pitts <lucienmp.qemu@gmail.com>
Cc: Richard Henderson <richard.henderson@linaro.org>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: RFC: Why dont we move to newer capstone?
Date: Sat, 5 Oct 2019 14:33:34 +0100	[thread overview]
Message-ID: <CAFEAcA-gLHm0D6vR0Rvpbi_bbVWpKspvm8YLSVPHpCVP6HmDUg@mail.gmail.com> (raw)
In-Reply-To: <CALvKS=GB1-zDnkKxei6Dn5MNyr5kwj+vEtD_3MZyVNfzqQuRZg@mail.gmail.com>

On Sat, 5 Oct 2019 at 11:21, Lucien Murray-Pitts
<lucienmp.qemu@gmail.com> wrote:
> Whilst working on a m68k patch I noticed that the capstone in use
> today (3.0) doesnt support the M68K and thus a hand turned disasm
> function is used.
>
> The newer capstone (5.0) appears to support a few more CPU, inc. m68k.
>
> Why we move to this newer capstone?

Moving to a newer capstone sounds like a good idea. The only
reason we haven't moved forward as far as I'm aware is that
nobody has done the work to send a patch to do that move
forward to the newer version. Richard Henderson would
probably know if there was any other blocker.

> Furthermore, if making a move why not move to something with wider cpu
> support like libopcodes  ?

Unfortunately as far as I know libopcodes is GPLv3, which is not
compatible with the GPLv2-only code in QEMU. Otherwise it
would be an obvious choice.

thanks
-- PMM


  reply	other threads:[~2019-10-05 13:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-05 10:11 RFC: Why dont we move to newer capstone? Lucien Murray-Pitts
2019-10-05 10:20 ` Lucien Murray-Pitts
2019-10-05 13:33   ` Peter Maydell [this message]
2019-10-15  8:27     ` Daniel P. Berrangé
2019-10-15  8:36       ` Thomas Huth
2019-10-15  8:47         ` Daniel P. Berrangé
2019-10-15  9:02           ` Marc-André Lureau
2019-10-15  9:14             ` Daniel P. Berrangé
2019-10-15  9:57               ` Peter Maydell
2019-10-15 10:12                 ` Daniel P. Berrangé
2019-10-14 23:46 ` Richard Henderson

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-gLHm0D6vR0Rvpbi_bbVWpKspvm8YLSVPHpCVP6HmDUg@mail.gmail.com \
    --to=peter.maydell@linaro.org \
    --cc=lucienmp.qemu@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.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 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.