From: Richard Henderson <richard.henderson@linaro.org>
To: mrm94040@yahoo.com, qemu-devel@nongnu.org
Subject: Re: Disassembler location
Date: Wed, 10 Jul 2024 14:56:42 -0700 [thread overview]
Message-ID: <bb7c5d11-f358-4680-9418-cbb8d596e943@linaro.org> (raw)
In-Reply-To: <709543045.677058.1720634520917@mail.yahoo.com>
On 7/10/24 11:02, Michael Morrell wrote:
> I'm working on a port to a new architecture and was noticing a discrepancy in where the disassembler code lives. There is a file "target/<arch>/disas.c" for 4 architectures (avr, loongarch, openrisc, and rx), but a file "disas/<arch>.c" for 14 architectures (if I counted right). It seems the 4 architectures using "target/<arch>/disas.c" are more recently added so I was wondering if that is now the preferred location. I couldn't find information on this, but I wasn't sure where to look.
>
> Any advice?
The older disas/arch.c files come from binutils, prior to the GPLv3 license change. These
are generally very old architectures, or not up to date.
The newer target/arch/disas.c are for architectures for which the translator and the
disassembler share generated code via decodetree. If you're implementing a new
architecture from scratch, this is your best choice.
The "best" supported are those with support in system libcapstone. :-)
r~
next prev parent reply other threads:[~2024-07-10 21:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <709543045.677058.1720634520917.ref@mail.yahoo.com>
2024-07-10 18:02 ` Disassembler location Michael Morrell
2024-07-10 21:55 ` Paolo Bonzini
2024-07-10 21:57 ` Richard Henderson
2024-07-10 21:56 ` Richard Henderson [this message]
2024-07-11 7:00 ` 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=bb7c5d11-f358-4680-9418-cbb8d596e943@linaro.org \
--to=richard.henderson@linaro.org \
--cc=mrm94040@yahoo.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).