From: Eli Zaretskii <eliz@gnu.org>
To: Anton Kolesov <Anton.Kolesov@synopsys.com>
Cc: gdb-patches@sourceware.org, Francois.Bedard@synopsys.com
Subject: Re: [PATCH 4/5] arc: Add disassembler helper
Date: Tue, 14 Feb 2017 15:50:00 -0000 [thread overview]
Message-ID: <837f4s22m0.fsf@gnu.org> (raw)
In-Reply-To: <20170214100130.29194-4-Anton.Kolesov@synopsys.com> (message from Anton Kolesov on Tue, 14 Feb 2017 13:01:29 +0300)
> From: Anton Kolesov <Anton.Kolesov@synopsys.com>
> Cc: Anton Kolesov <Anton.Kolesov@synopsys.com>, Francois Bedard <Francois.Bedard@synopsys.com>
> Date: Tue, 14 Feb 2017 13:01:29 +0300
>
> Add disassembler helper for GDB, that uses opcodes structure arc_instruction
> and adds convenience functions to handle instruction operands. This interface
> solves at least those problems with arc_instruction:
>
> * Some instructions, like "push_s", have implicit operands which are not
> directly present in arc_instruction.
> * Operands of particular meaning, like branch/jump targets, have various
> locations and meaning depending on type of branch/target.
> * Access to operand value is abstracted into a separate function, so callee
> code shouldn't bother if operand value is an immediate value or in a
> register.
>
> Testcases included in this commit are fairly limited - they test exclusively
> branch instructions, something that will be used in software single stepping.
> Most of the other parts of this disassembler helper are tested during prologue
> analysis testing.
>
> gdb/ChangeLog:
>
> yyyy-mm-dd Anton Kolesov <anton.kolesov@synopsys.com>
>
> * configure.tgt: Add arc-insn.o.
> * arc-tdep.c (arc_delayed_print_insn): Make non-static.
> (dump_arc_instruction_command): New function.
> * arc-tdep.h (arc_delayed_print_insn): Add function declaration.
> * arch/arc-insn.c: New file.
> * arch/arc-insn.h: Likewise.
>
> gdb/doc/ChangeLog:
>
> yyyy-mm-dd Anton Kolesov <anton.kolesov@synopsys.com>
>
> * gdb.texinfo (Synopsys ARC): Add "maint print arc arc-instruction".
>
> gdb/testsuite/ChangeLog:
>
> yyyy-mm-dd Anton Kolesov <anton.kolesov@synopsys.com>
>
> * gdb.arch/arc-decode-insn.S: New file.
> * gdb.arch/arc-decode-insn.exp: Likewise.
OK for the documentation part.
Thanks.
next prev parent reply other threads:[~2017-02-14 15:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-14 10:01 [PATCH 1/5] arc: Align internal regnums with architectural regnums Anton Kolesov
2017-02-14 10:01 ` [PATCH 3/5] arc: Add "maintenance print arc" command prefix Anton Kolesov
2017-02-17 13:02 ` Pedro Alves
2017-02-14 10:01 ` [PATCH 2/5] arc: Set section to ".text" when disassembling Anton Kolesov
2017-02-15 22:27 ` Yao Qi
2017-02-16 16:35 ` Anton Kolesov
2017-02-17 12:31 ` Pedro Alves
2017-03-15 15:16 ` Anton Kolesov
2017-02-14 10:01 ` [PATCH 5/5] arc: Add prologue analysis Anton Kolesov
2017-02-14 15:51 ` Eli Zaretskii
2017-02-17 13:25 ` Pedro Alves
2017-03-15 15:18 ` [PATCH 5/5 v2] " Anton Kolesov
2017-03-15 15:59 ` Eli Zaretskii
2017-03-27 14:20 ` Anton Kolesov
2017-03-28 13:28 ` Pedro Alves
2017-02-14 10:01 ` [PATCH 4/5] arc: Add disassembler helper Anton Kolesov
2017-02-14 15:50 ` Eli Zaretskii [this message]
2017-02-17 13:00 ` Pedro Alves
2017-02-17 13:01 ` Pedro Alves
2017-02-17 13:26 ` [PATCH 1/5] arc: Align internal regnums with architectural regnums Pedro Alves
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=837f4s22m0.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=Anton.Kolesov@synopsys.com \
--cc=Francois.Bedard@synopsys.com \
--cc=gdb-patches@sourceware.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