Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Maxim Grigoriev <maxim@tensilica.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: [commit] Correct style issues in xtensa-tdep.c
Date: Fri, 11 Mar 2011 21:04:00 -0000	[thread overview]
Message-ID: <4D7A6B9D.90408@tensilica.com> (raw)
In-Reply-To: <20110311064501.GA30306@adacore.com>

[-- Attachment #1: Type: text/plain, Size: 918 bytes --]

I am surprised I missed it. Thanks for noticing this.
This patch corrects the style violation mentioned by Joel.

On 03/10/2011 10:45 PM, Joel Brobecker wrote:
>> 2011-03-10  Maxim Grigoriev<maxim2405@gmail.com>
>>
>> 	* xtensa-tdep.c (windowing_enabled): Remove inline attribute.
>> 	(xtensa_write_register, xtensa_read_register): Likewise.
>> 	(xtensa_hextochar): Removed.
>> 	(xtensa_init_reggroups): Replace xtensa_hextochar () by explicit code.
>>      
> Small comments, seen while scanning your patch...
>
>    
>> -static inline void warning_once ()
>> +static void warning_once ()
>>      
> The function name should be on the first column of the line.
> This is to facilitate the search of the function implementation
> (we can use:<<grep "^warning_once">>  for instance). Also,
> functions with no arguments should be declared with a "void"
> parameter. Thus:
>
> static void
> warning_once (void)
>
>    


[-- Attachment #2: Style.diff --]
[-- Type: text/plain, Size: 686 bytes --]

2011-03-11  Maxim Grigoriev  <maxim2405@gmail.com>

	* xtensa-tdep.c (warning_once): Correct style issues.

Index: gdb/xtensa-tdep.c
===================================================================
RCS file: /cvs/src/src/gdb/xtensa-tdep.c,v
retrieving revision 1.54
diff -u -r1.54 xtensa-tdep.c
--- gdb/xtensa-tdep.c	11 Mar 2011 02:32:31 -0000	1.54
+++ gdb/xtensa-tdep.c	11 Mar 2011 18:25:19 -0000
@@ -1421,7 +1421,8 @@
 /* Report a problem with prologue analysis while doing backtracing.
    But, do it only once to avoid annoyng repeated messages.  */
 
-static void warning_once ()
+static void
+warning_once (void)
 {
   if (xtensa_session_once_reported == 0)
     warning (_("\

      parent reply	other threads:[~2011-03-11 18:36 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-11  4:20 [commit] Get rid of build warnings on xtensa-tdep.c Maxim Grigoriev
2011-03-11  7:59 ` Joel Brobecker
2011-03-11 11:39   ` [RFA] New rules for ARI (was [commit] Get rid of build warnings on xtensa-tdep.c) Pierre Muller
2011-03-11 14:21     ` Joel Brobecker
2011-03-11 14:51       ` Pierre Muller
     [not found]   ` <41860.1858466447$1299837420@news.gmane.org>
2011-03-11 17:07     ` [RFA] New rules for ARI Tom Tromey
2011-03-16 14:23       ` Joel Brobecker
2011-03-16 14:41         ` Pedro Alves
2011-03-16 15:25           ` Tom Tromey
2011-03-16 15:54             ` Pedro Alves
2011-03-16 16:03               ` Tom Tromey
2011-03-16 16:14                 ` Pedro Alves
2011-03-16 17:11                   ` Tom Tromey
2011-03-16 17:11                     ` Pedro Alves
2011-03-16 17:27                       ` Tom Tromey
2011-03-16 17:42                         ` Pedro Alves
2011-03-16 15:18         ` Tom Tromey
2011-03-11 21:04   ` Maxim Grigoriev [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=4D7A6B9D.90408@tensilica.com \
    --to=maxim@tensilica.com \
    --cc=brobecker@adacore.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