* Updates on libcapstone?
@ 2020-07-09 13:07 Philippe Mathieu-Daudé
2020-07-10 19:30 ` Richard Henderson
0 siblings, 1 reply; 3+ messages in thread
From: Philippe Mathieu-Daudé @ 2020-07-09 13:07 UTC (permalink / raw)
To: qemu-devel, Richard Henderson
Cc: Peter Maydell, Thomas Huth, Daniel P . Berrange
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.
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: Updates on libcapstone?
2020-07-09 13:07 Updates on libcapstone? Philippe Mathieu-Daudé
@ 2020-07-10 19:30 ` Richard Henderson
2020-07-13 10:12 ` Thomas Huth
0 siblings, 1 reply; 3+ messages in thread
From: Richard Henderson @ 2020-07-10 19:30 UTC (permalink / raw)
To: Philippe Mathieu-Daudé, qemu-devel
Cc: Peter Maydell, Thomas Huth, Daniel P . Berrange
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~
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Updates on libcapstone?
2020-07-10 19:30 ` Richard Henderson
@ 2020-07-13 10:12 ` Thomas Huth
0 siblings, 0 replies; 3+ messages in thread
From: Thomas Huth @ 2020-07-13 10:12 UTC (permalink / raw)
To: Richard Henderson, Philippe Mathieu-Daudé, qemu-devel
Cc: Peter Maydell, Daniel P . Berrange, Stefan Hajnoczi
On 10/07/2020 21.30, Richard Henderson wrote:
> 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...
Maybe a nice topic for the next GSoC?
Thomas
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2020-07-13 10:16 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2020-07-09 13:07 Updates on libcapstone? Philippe Mathieu-Daudé
2020-07-10 19:30 ` Richard Henderson
2020-07-13 10:12 ` Thomas Huth
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).