qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Richard Henderson <richard.henderson@linaro.org>
To: Lucien Murray-Pitts <lucienmp.qemu@gmail.com>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: RFC: Why dont we move to newer capstone?
Date: Mon, 14 Oct 2019 16:46:39 -0700	[thread overview]
Message-ID: <f243dfe0-f04f-1936-5ca0-a89aaf3b83db@linaro.org> (raw)
In-Reply-To: <CALvKS=E-t1c+BVDn=0RbM8nBry8GcYOXh-PrziQO7XhS7W2NUw@mail.gmail.com>

On 10/5/19 3:11 AM, Lucien Murray-Pitts wrote:
> Hi folks,
> 
> 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.

I don't see a capstone v5.  The latest I see is v4.1.

> Why we move to this newer capstone?

I had some patches for that floating about in May, but
it missed the merge window for qemu 4.1.

Thanks for reminding me about them.


r~


      parent reply	other threads:[~2019-10-14 23:48 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
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 [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=f243dfe0-f04f-1936-5ca0-a89aaf3b83db@linaro.org \
    --to=richard.henderson@linaro.org \
    --cc=lucienmp.qemu@gmail.com \
    --cc=qemu-devel@nongnu.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 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).