From: Claudio Fontana <claudio.fontana@huawei.com>
To: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: Peter Maydell <peter.maydell@linaro.org>
Subject: [Qemu-devel] [RFC 0/4] ARM aarch64 disas output libvixl support
Date: Wed, 11 Sep 2013 14:54:32 +0200 [thread overview]
Message-ID: <52306808.4030701@huawei.com> (raw)
This is the aarch64 libvixl support patchset in the current state.
It provides (limited) support for disassembly output on aarch64.
Only host disassembly is enabled, since target for aarch64 is not in yet.
An external objdump solution as exemplified before by R.H. seems preferable
to me, even if it means giving up the monitor support.
I'd rather have correct output from -d.
The run time need for debugging assembly is already fulfilled by gdb better
than the monitor.
libvixl does not support many opcodes right now, is C++, and it is documented
as working only for a 64bit host with a LP64 memory model.
Claudio Fontana (4):
configure: add c++ compiler support
rules.mak: support C++ compiling and linking
disas: add libvixl source code for aarch64
disas: implement host disassembly output for aarch64
configure | 21 +
disas.c | 2 +
disas/Makefile.objs | 7 +
disas/aarch64-cxx.cc | 53 +
disas/aarch64.c | 45 +
disas/libvixl/LICENCE | 30 +
disas/libvixl/Makefile.objs | 6 +
disas/libvixl/README.md | 128 ++
disas/libvixl/doc/changelog.md | 12 +
disas/libvixl/doc/supported-instructions.md | 1133 ++++++++++++++
disas/libvixl/src/a64/assembler-a64.cc | 2172 ++++++++++++++++++++++++++
disas/libvixl/src/a64/assembler-a64.h | 1784 +++++++++++++++++++++
disas/libvixl/src/a64/constants-a64.h | 1104 +++++++++++++
disas/libvixl/src/a64/cpu-a64.cc | 148 ++
disas/libvixl/src/a64/cpu-a64.h | 56 +
disas/libvixl/src/a64/debugger-a64.cc | 1511 ++++++++++++++++++
disas/libvixl/src/a64/debugger-a64.h | 188 +++
disas/libvixl/src/a64/decoder-a64.cc | 712 +++++++++
disas/libvixl/src/a64/decoder-a64.h | 198 +++
disas/libvixl/src/a64/disasm-a64.cc | 1678 ++++++++++++++++++++
disas/libvixl/src/a64/disasm-a64.h | 109 ++
disas/libvixl/src/a64/instructions-a64.cc | 238 +++
disas/libvixl/src/a64/instructions-a64.h | 344 ++++
disas/libvixl/src/a64/instrument-a64.cc | 638 ++++++++
disas/libvixl/src/a64/instrument-a64.h | 108 ++
disas/libvixl/src/a64/macro-assembler-a64.cc | 1108 +++++++++++++
disas/libvixl/src/a64/macro-assembler-a64.h | 1175 ++++++++++++++
disas/libvixl/src/a64/simulator-a64.cc | 2077 ++++++++++++++++++++++++
disas/libvixl/src/a64/simulator-a64.h | 576 +++++++
disas/libvixl/src/globals.h | 66 +
disas/libvixl/src/platform.h | 43 +
disas/libvixl/src/utils.cc | 120 ++
disas/libvixl/src/utils.h | 126 ++
include/disas/bfd.h | 1 +
rules.mak | 24 +-
35 files changed, 17737 insertions(+), 4 deletions(-)
create mode 100644 disas/aarch64-cxx.cc
create mode 100644 disas/aarch64.c
create mode 100644 disas/libvixl/LICENCE
create mode 100644 disas/libvixl/Makefile.objs
create mode 100644 disas/libvixl/README.md
create mode 100644 disas/libvixl/doc/changelog.md
create mode 100644 disas/libvixl/doc/supported-instructions.md
create mode 100644 disas/libvixl/src/a64/assembler-a64.cc
create mode 100644 disas/libvixl/src/a64/assembler-a64.h
create mode 100644 disas/libvixl/src/a64/constants-a64.h
create mode 100644 disas/libvixl/src/a64/cpu-a64.cc
create mode 100644 disas/libvixl/src/a64/cpu-a64.h
create mode 100644 disas/libvixl/src/a64/debugger-a64.cc
create mode 100644 disas/libvixl/src/a64/debugger-a64.h
create mode 100644 disas/libvixl/src/a64/decoder-a64.cc
create mode 100644 disas/libvixl/src/a64/decoder-a64.h
create mode 100644 disas/libvixl/src/a64/disasm-a64.cc
create mode 100644 disas/libvixl/src/a64/disasm-a64.h
create mode 100644 disas/libvixl/src/a64/instructions-a64.cc
create mode 100644 disas/libvixl/src/a64/instructions-a64.h
create mode 100644 disas/libvixl/src/a64/instrument-a64.cc
create mode 100644 disas/libvixl/src/a64/instrument-a64.h
create mode 100644 disas/libvixl/src/a64/macro-assembler-a64.cc
create mode 100644 disas/libvixl/src/a64/macro-assembler-a64.h
create mode 100644 disas/libvixl/src/a64/simulator-a64.cc
create mode 100644 disas/libvixl/src/a64/simulator-a64.h
create mode 100644 disas/libvixl/src/globals.h
create mode 100644 disas/libvixl/src/platform.h
create mode 100644 disas/libvixl/src/utils.cc
create mode 100644 disas/libvixl/src/utils.h
--
1.8.1
next reply other threads:[~2013-09-11 12:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-11 12:54 Claudio Fontana [this message]
2013-09-11 12:59 ` [Qemu-devel] [RFC 1/4] configure: add c++ compiler support Claudio Fontana
2013-09-11 13:02 ` [Qemu-devel] [RFC 2/4] rules.mak: support C++ compiling and linking Claudio Fontana
2013-09-11 13:05 ` [Qemu-devel] [RFC 3/4] disas: add libvixl source code for aarch64 Claudio Fontana
2013-09-11 13:08 ` [Qemu-devel] [RFC 4/4] disas: implement host disassembly output " Claudio Fontana
2013-09-16 6:53 ` Andreas Färber
2013-09-16 10:43 ` Claudio Fontana
2013-09-11 13:14 ` [Qemu-devel] [RFC 0/4] ARM aarch64 disas output libvixl support Andreas Färber
2013-09-11 13:29 ` Peter Maydell
2013-09-11 13:37 ` Peter Maydell
2013-09-11 14:35 ` [Qemu-devel] [RFC 3/4] disas: add libvixl source code for aarch64 Claudio Fontana
2013-09-15 16:41 ` [Qemu-devel] [RFC 0/4] ARM aarch64 disas output libvixl support Rob Landley
2013-09-15 17:27 ` Peter Maydell
2013-09-15 20:04 ` Laurent Desnogues
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=52306808.4030701@huawei.com \
--to=claudio.fontana@huawei.com \
--cc=peter.maydell@linaro.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).