From: Rot127 <unisono@quyllur.org>
To: qemu-devel@nongnu.org
Subject: [Capstone] Feedback request for new architecture updater
Date: Thu, 12 Jan 2023 11:24:55 -0500 [thread overview]
Message-ID: <c4ec12d4-e07c-ada9-5cec-744dae7c069b@quyllur.org> (raw)
I currently work on a new updater for architecture modules in Capstone.
The current update process has the problem that it is a lot of manual work.
Syncing the information from LLVM to Capstone requires a one to
translate a lot of C++ to C code and fix a ton of build errors.
This lead to architecture modules not getting updated. So there are many
new instructions in Capstone which are not supported.
The new updater will take away as much manual work as possible.
It does this by translating most C++ to C via a little translation tool
and uses refactored LLVM-TableGen backends which emit directly the code
Capstone needs.
Currently it is in a early stage but it is ready to receive some feedback.
If anyone finds the time to take a look at it and write down their
thoughts, suggestions or improvement ideas, I would be very grateful.
Capstone draft PR: https://github.com/capstone-engine/capstone/pull/1949
next reply other threads:[~2023-01-12 16:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-12 16:24 Rot127 [this message]
2023-01-13 9:27 ` [Capstone] Feedback request for new architecture updater Thomas Huth
2023-01-13 17:32 ` Rot127
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=c4ec12d4-e07c-ada9-5cec-744dae7c069b@quyllur.org \
--to=unisono@quyllur.org \
--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).