qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: qemu-devel <qemu-devel@nongnu.org>,
	Richard Henderson <richard.henderson@linaro.org>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Thomas Huth <thuth@redhat.com>,
	"Daniel P . Berrange" <berrange@redhat.com>
Subject: Updates on libcapstone?
Date: Thu, 9 Jul 2020 15:07:58 +0200	[thread overview]
Message-ID: <16ea7c6b-d959-9df2-0603-d07e40ff4021@redhat.com> (raw)

Hi Richard,

We are using libcapstone since almost 3 years for the arm/i386/ppc
'base' architectures.
The library is still optional in ./configure.
I wonder if we can make it a strong requisite, this way we could
get rid of disas/{arm.c,arm-a64.cc,i386.c,ppc.c} and the disas/libvixl
submodule, then having C++ compiler is not necessary anymore.

As of the release 4.0, the list of supported architectures is:

"ARM, ARM64 (ARMv8), Ethereum VM, M68K, Mips, PPC, Sparc, SystemZ,
TMS320C64X, M680X, XCore and X86 (including X86_64)."

m68k/mips/sparc/s390x are other candidates.

I remember you had a series related to capstone, but eventually there
was a problem so you postponed it until some patches were merged
upstream, do you remember?

Thanks for any update,

Phil.



             reply	other threads:[~2020-07-09 13:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-09 13:07 Philippe Mathieu-Daudé [this message]
2020-07-10 19:30 ` Updates on libcapstone? Richard Henderson
2020-07-13 10:12   ` Thomas Huth

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=16ea7c6b-d959-9df2-0603-d07e40ff4021@redhat.com \
    --to=philmd@redhat.com \
    --cc=berrange@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.org \
    --cc=thuth@redhat.com \
    /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).