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 5/5] arc: Add prologue analysis
Date: Tue, 14 Feb 2017 15:51:00 -0000 [thread overview]
Message-ID: <8360kc22jw.fsf@gnu.org> (raw)
In-Reply-To: <20170214100130.29194-5-Anton.Kolesov@synopsys.com> (message from Anton Kolesov on Tue, 14 Feb 2017 13:01:30 +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:30 +0300
>
> Add a prologue analysis that recognizes all instructions that may happen in
> compiler-generated prologue, including various stores, core register moves,
> subtraction and ENTER_S instruction that does a lot of prologue actions through
> microcode.
>
> Testcases cover various prologue scenarios, including instructions that are
> spread across multiple 16-bit encodings (for example there are 7 encodings of
> store instruction).
>
> gdb/ChangeLog:
>
> yyyy-mm-dd Anton Kolesov <anton.kolesov@synopsys.com>
>
> * arc-tdep.c (arc_frame_cache): Add support for prologue analysis.
> (arc_skip_prologue): Likewise.
> (arc_make_frame_cache): Likewise.
> (arc_pv_get_operand): New function.
> (arc_is_in_prologue): Likewise.
> (arc_fprintf_disasm): Likewise.
> (arc_disassemble_info): Likewise.
> (arc_analyze_prologue): Likewise.
> (arc_print_frame_cache): Likewise.
> (MAX_PROLOGUE_LENGTH): New constant.
>
> gdb/doc/ChangeLog:
>
> yyyy-mm-dd Anton Kolesov <anton.kolesov@synopsys.com>
>
> * gdb.texinfo (Synopsys ARC): Document "set debug arc 2".
>
> gdb/testsuite/ChangeLog:
> yyyy-mm-dd Anton Kolesov <anton.kolesov@synopsys.com>
>
> * gdb.arch/arc-analyze-prologue.S: New file.
> * gdb.arch/arc-analyze-prologue.exp: Likewise.
OK for the documentation part.
Thanks.
next prev parent reply other threads:[~2017-02-14 15:51 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 4/5] arc: Add disassembler helper Anton Kolesov
2017-02-14 15:50 ` Eli Zaretskii
2017-02-17 13:00 ` Pedro Alves
2017-02-17 13:01 ` Pedro Alves
2017-02-14 10:01 ` [PATCH 5/5] arc: Add prologue analysis Anton Kolesov
2017-02-14 15:51 ` Eli Zaretskii [this message]
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 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 3/5] arc: Add "maintenance print arc" command prefix Anton Kolesov
2017-02-17 13:02 ` 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=8360kc22jw.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