From: Ajit Kumar Agarwal <ajit.kumar.agarwal@xilinx.com>
To: Yao Qi <yao@codesourcery.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Cc: Joel Brobecker <brobecker@adacore.com>,
Michael Eager <eager@eagercon.com>,
Vinod Kathail <vinodk@xilinx.com>,
Vidhumouli Hunsigida <vidhum@xilinx.com>,
Nagaraju Mekala <nmekala@xilinx.com>
Subject: RE: [Patch, microblaze]: Add slr and shr regs
Date: Fri, 23 May 2014 20:33:00 -0000 [thread overview]
Message-ID: <b483a50a-cf2a-476b-953c-a889d9c46f15@BL2FFO11FD015.protection.gbl> (raw)
In-Reply-To: <537F0705.3010807@codesourcery.com>
-----Original Message-----
From: Yao Qi [mailto:yao@codesourcery.com]
Sent: Friday, May 23, 2014 2:00 PM
To: Ajit Kumar Agarwal; gdb-patches@sourceware.org
Cc: Joel Brobecker; Michael Eager; Vinod Kathail; Vidhumouli Hunsigida; Nagaraju Mekala
Subject: Re: [Patch, microblaze]: Add slr and shr regs
On 05/23/2014 02:53 PM, Ajit Kumar Agarwal wrote:
> +microblaze-linux.c : $(srcdir)/../regformats/reg-microblaze.dat $(regdat_sh)
> + $(SHELL) $(regdat_sh) $(srcdir)/../regformats/reg-microblaze.dat
> +mips-linux.c
^^^^^^^^^^^^ Typo.
> mips-dsp-linux.c : $(srcdir)/../regformats/mips-dsp-linux.dat $(regdat_sh)
> $(SHELL) $(regdat_sh) $(srcdir)/../regformats/mips-dsp-linux.dat
> mips-dsp-linux.c mips64-linux.c :
> $(srcdir)/../regformats/mips64-linux.dat $(regdat_sh)
> diff --git a/gdb/regformats/reg-microblaze.dat
> b/gdb/regformats/reg-microblaze.dat
> new file mode 100644
> index 0000000..936bc44
> --- /dev/null
> +++ b/gdb/regformats/reg-microblaze.dat
> @@ -0,0 +1,41 @@
> +name:microblaze
> +expedite:r1,pc
> +32:r0
>>The more important thing is microblaze-linux.c and reg-microblaze.dat should be generated by some .xml file in gdb/features/ directory. If that is intended, please add the .xml files, >>and generate the .c file and .dat file in regformats/ directory.
I will incorporate the above changes.
Thanks & Regards
Ajit
--
Yao (齐尧)
next prev parent reply other threads:[~2014-05-23 20:33 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-23 6:54 Ajit Kumar Agarwal
2014-05-23 7:34 ` Michael Eager
2014-05-23 9:47 ` Ajit Kumar Agarwal
2014-05-23 22:42 ` Michael Eager
2014-05-26 10:04 ` Ajit Kumar Agarwal
2014-05-27 6:34 ` Michael Eager
2014-05-27 7:46 ` Ajit Kumar Agarwal
2014-05-27 8:53 ` Pedro Alves
2014-06-09 17:26 ` Ajit Kumar Agarwal
2014-06-09 17:57 ` Pedro Alves
2014-06-09 19:35 ` Ajit Kumar Agarwal
2014-05-29 7:20 ` Michael Eager
2014-06-05 15:54 ` Michael Eager
2014-06-09 17:26 ` Ajit Kumar Agarwal
2014-06-09 18:28 ` Michael Eager
2014-06-09 19:31 ` Ajit Kumar Agarwal
2014-06-09 20:06 ` Michael Eager
2014-06-10 13:51 ` Ajit Kumar Agarwal
2014-06-10 14:12 ` Michael Eager
2014-06-10 14:49 ` Ajit Kumar Agarwal
2014-06-10 15:27 ` Michael Eager
2014-06-12 8:34 ` Ajit Kumar Agarwal
2014-05-23 8:32 ` Yao Qi
2014-05-23 20:33 ` Ajit Kumar Agarwal [this message]
2014-05-23 8:44 ` Pedro Alves
2014-05-23 20:36 ` Ajit Kumar Agarwal
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=b483a50a-cf2a-476b-953c-a889d9c46f15@BL2FFO11FD015.protection.gbl \
--to=ajit.kumar.agarwal@xilinx.com \
--cc=brobecker@adacore.com \
--cc=eager@eagercon.com \
--cc=gdb-patches@sourceware.org \
--cc=nmekala@xilinx.com \
--cc=vidhum@xilinx.com \
--cc=vinodk@xilinx.com \
--cc=yao@codesourcery.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).