From: Michael Eager <eager@eagercon.com>
To: Ajit Kumar Agarwal <ajit.kumar.agarwal@xilinx.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Cc: Vinod Kathail <vinodk@xilinx.com>,
Vidhumouli Hunsigida <vidhum@xilinx.com>,
Nagaraju Mekala <nmekala@xilinx.com>
Subject: Re: [Patch, Microblaze]: Added support of shr and slr regs, little endian breakpoints,backtrace support and communicate with larger blocks.
Date: Tue, 20 May 2014 21:09:00 -0000 [thread overview]
Message-ID: <537BC483.2030506@eagercon.com> (raw)
In-Reply-To: <57db2c05-1b1a-472b-9182-5ce078e8805a@BY2FFO11FD055.protection.gbl>
On 05/20/14 01:17, Ajit Kumar Agarwal wrote:
> Hello All:
>
> This patch added the support of shr and slr regs and little endian breakpoints,
> backtrace support without debug information and communicate larger blocks with
> debugging agent.
There seem to be multiple unrelated changes combined into one patch.
Submit each independent change as a separate patch.
>
> ChangeLog:
> 2014-05-20 Ajit Agarwal <ajitkum@xilinx.com>
>
> * gdb/gdbserver/Makefile.in (microblaze-linux.c) : New target
>
> * gdb/microblaze-tdep.c
> (microblaze_register_names): Added the rshr and rslr register names.
> (microblaze_breakpoint_from_pc): Added Declaration of byte_order
> and break_insn_le. Check of byte order by BFD_ENDIAN_BIG
> (microblaze_alloc_frame_cache): Initialize saved_sp
> (microblaze_analyze_prologue): Do a block read to minimize the
> transaction with debug agent. Use of target_read_memory. Freeing
> the block read.
Please read the GNU document describing how to write a Change Log entry.
You don't need to give a prose description explaining the changes.
Read the ChangeLog for examples.
--
Michael Eager eager@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306 650-325-8077
prev parent reply other threads:[~2014-05-20 21:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-20 8:17 Ajit Kumar Agarwal
2014-05-20 13:13 ` Joel Brobecker
2014-05-20 14:15 ` Ajit Kumar Agarwal
2014-05-20 14:35 ` Joel Brobecker
2014-05-20 21:09 ` Michael Eager [this message]
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=537BC483.2030506@eagercon.com \
--to=eager@eagercon.com \
--cc=ajit.kumar.agarwal@xilinx.com \
--cc=gdb-patches@sourceware.org \
--cc=nmekala@xilinx.com \
--cc=vidhum@xilinx.com \
--cc=vinodk@xilinx.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