From: Yao Qi <qiyaoltc@gmail.com>
To: marcus.shawcroft@gmail.com
Cc: gdb-patches@sourceware.org, binutils@sourceware.org
Subject: [PATCH 0/3 V2] [aarch64] Use opcodes to decode instructions in GDB
Date: Fri, 02 Oct 2015 11:24:00 -0000 [thread overview]
Message-ID: <1443785039-24602-1-git-send-email-yao.qi@linaro.org> (raw)
In-Reply-To: <CAFqB+Px8-V8eojj8T66_zrM6krPeGXBVLU9h+_j5yEcrk0MMJg@mail.gmail.com>
Hi Marcus,
On 02/10/15 08:51, Marcus Shawcroft wrote:
> I'll let others comment on the gdb aspect of this patch, w.r.t
> opcodes, the aarch64-dis.h header is internal to opcodes. The public
> interface to opcodes is exposed via include/opcode/aarch64.h or
> include/dis-asm.h. The latter exposes just the cross architecture
> disassembler interface so I think includes/opcode/aarch64.h is the
> right choice in this case.
OK, I move the declaration to includes/opcode/aarch64.h in V2.
>
> Before we expose this function, can we put in a patch to rename it to
> following the name space convention used by the other exposed
> functions, something like aarch64_disassemble_insn.? I think we should
Patch #2 in V2 does this, but renames it to aarch64_decode_insn,
because aarch64_decode_insn can be used in disassemble, but also in
something else.
> take the patch to drop the PC argument first, then rename and expose
> the function, then the gdb patch to use the interface.
OK, in V2, there are three patches. Patch #1 remove the PC argument,
patch #2 exposes and renames disas_aarch64_insn, and patch #3 use it
GDB.
>
>> >+/* Decode INSN and fill in *INST the instruction information. Return zero
>> >+ on success. */
>> >+
>> >+int disas_aarch64_insn (uint32_t insn, aarch64_inst *inst);
> The prototype should drop the formal argument names, irrespective of
> which .h file it lands in.
Fixed in V2.
*** BLURB HERE ***
Yao Qi (3):
[aarch64] Remove argument pc from disas_aarch64_insn
[aarch64] expose disas_aarch64_insn and rename it to
aarch64_decode_insn
[aarch64] use aarch64_decode_insn to decode instructions in GDB
gdb/aarch64-tdep.c | 29 ++++++++++++++++++-----------
include/opcode/aarch64.h | 3 +++
opcodes/aarch64-dis.c | 10 +++++-----
3 files changed, 26 insertions(+), 16 deletions(-)
--
1.9.1
next prev parent reply other threads:[~2015-10-02 11:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-01 16:35 [PATCH 0/2] " Yao Qi
2015-10-01 16:35 ` [PATCH 1/2] [aarch64] Remove argument pc from disas_aarch64_insn Yao Qi
2015-10-01 16:36 ` [PATCH 2/2] [aarch64] Use opcodes to decode instructions in GDB Yao Qi
2015-10-02 7:51 ` Marcus Shawcroft
2015-10-02 11:24 ` Yao Qi [this message]
2015-10-02 11:24 ` [PATCH 3/3] [aarch64] use aarch64_decode_insn " Yao Qi
2015-10-07 8:56 ` Yao Qi
2015-10-02 11:24 ` [PATCH 1/3] [aarch64] Remove argument pc from disas_aarch64_insn Yao Qi
2015-10-02 12:30 ` Marcus Shawcroft
2015-10-02 11:24 ` [PATCH 2/3] [aarch64] expose disas_aarch64_insn and rename it to aarch64_decode_insn Yao Qi
2015-10-02 12:35 ` Marcus Shawcroft
2015-10-02 14:32 ` Yao Qi
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=1443785039-24602-1-git-send-email-yao.qi@linaro.org \
--to=qiyaoltc@gmail.com \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=marcus.shawcroft@gmail.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