From: Michael Eager <eager@eagercon.com>
To: Ajit Kumar Agarwal <ajit.kumar.agarwal@xilinx.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Cc: Vinod Kathail <vinodk@xilinx.com>,
Vidhumouli Hunsigida <vidhum@xilinx.com>,
Nagaraju Mekala <nmekala@xilinx.com>
Subject: Re: [Patch,Microblaze]: Added Break Handler Support
Date: Tue, 13 May 2014 17:00:00 -0000 [thread overview]
Message-ID: <53724F95.7090500@eagercon.com> (raw)
In-Reply-To: <fac736b9-9d73-4de2-8987-88200ac8b8ac@BN1BFFO11FD037.protection.gbl>
On 05/13/14 02:14, Ajit Kumar Agarwal wrote:
> Hello Michael:
>
> The following patch is to handle Software and Hardware breaks in Microblaze Architecture.
> Deja GNU testcase does not have any regressions and the testcase attached passes through.
> Review comments are incorporated.
>
> Okay for trunk?
Just saying OK would only be appropriate if you had write access to the repository.
> Added Break Handler support to incorporate the hardware and software break. The Break Handler routine
> will be generating the rtbd instruction. At the call point where the software breaks are generated with
> the instruction brki with register operand as r16.
>
> 2014-05-13 Ajit Agarwal <ajitkum@xilinx.com>
>
> * config/microblaze/microblaze.c
> (microblaze_break_function_p,microblaze_is_break_handler) : New
>
> * config/microblaze/microblaze.h (BREAK_HANDLER_NAME) : New macro
>
> * config/microblaze/microblaze.md :
> Extended support for generation of brki instruction and rtbd instruction.
A better ChangeLog entry is
* config/microblaze/microblaze.md (*<optab>,<optab>_internal):
Add microblaze_is_break_handler () test.
Give specifics, naming functions, rather than making general comments.
As the ChangeLog standard says:
It’s important to name the changed function or variable in full.
Don’t abbreviate function or variable names, and don’t combine them.
Subsequent maintainers will often search for a function name to find
all the change log entries that pertain to it; if you abbreviate the
name, they won’t find it when they search.
Mention each place where there are changes. There should be a ChangeLog
entry for each non-trivial change.
Your patch made four significant changes to microblaze.md.
There appear to be several changes in microblaze.c, not just the definition
of the new functions as shown in your entry.
> * config/microblaze/microblaze-protos.h
> (microblaze_break_function_p,microblaze_is_break_handler) : New Declaration.
>
> * testsuite/gcc.target/microblaze/others/break_handler.c : New.
Thanks for the test case.
As mentioned previously, add documentation for _break_handler.
> diff --git a/gcc/config/microblaze/microblaze-protos.h b/gcc/config/microblaze/microblaze-protos.h
> index b03e9e1..f3cc099 100644
> --- a/gcc/config/microblaze/microblaze-protos.h
> +++ b/gcc/config/microblaze/microblaze-protos.h
Please include the patch only once, not both inline and again as an
attachment.
--
Michael Eager eager@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306 650-325-8077
next prev parent reply other threads:[~2014-05-13 17:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <345d2b49-c710-4795-924b-217a5221921c@CO9EHSMHS012.ehs.local>
2014-05-06 15:00 ` Michael Eager
[not found] ` <5368F2DA.9090509@eagercon.com>
2014-05-13 9:15 ` Ajit Kumar Agarwal
2014-05-13 17:00 ` Michael Eager [this message]
2014-05-13 19:15 ` Ajit Kumar Agarwal
2014-05-13 19:24 ` Michael Eager
2014-05-13 21:42 ` Ajit Kumar Agarwal
2014-05-13 22:03 ` Michael Eager
2014-05-14 9:27 ` Ajit Kumar Agarwal
2014-05-17 15:14 ` Michael Eager
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=53724F95.7090500@eagercon.com \
--to=eager@eagercon.com \
--cc=ajit.kumar.agarwal@xilinx.com \
--cc=gcc-patches@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).