From: Richard Henderson <richard.henderson@linaro.org>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Thomas Huth <thuth@redhat.com>,
"Daniel P . Berrange" <berrange@redhat.com>
Subject: Re: Updates on libcapstone?
Date: Fri, 10 Jul 2020 12:30:20 -0700 [thread overview]
Message-ID: <a6301171-a296-c65c-8e59-6a98a7b3f2ed@linaro.org> (raw)
In-Reply-To: <16ea7c6b-d959-9df2-0603-d07e40ff4021@redhat.com>
On 7/9/20 6:07 AM, Philippe Mathieu-Daudé wrote:
> 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?
I do.
My biggest problem with libcapstone is that it doesn't have an automated way to
merge from upstream llvm, so it doesn't get any new architecture updates.
What I think we should do is drop libcapstone entirely, and use libllvm
directly. It's a bit more code to use, but llvm is where new architectures
(and architecture extensions) get merged.
A mere matter of coding...
r~
next prev parent reply other threads:[~2020-07-10 19:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-09 13:07 Updates on libcapstone? Philippe Mathieu-Daudé
2020-07-10 19:30 ` Richard Henderson [this message]
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=a6301171-a296-c65c-8e59-6a98a7b3f2ed@linaro.org \
--to=richard.henderson@linaro.org \
--cc=berrange@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.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).