Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: "'Abid, Hafiz'" <hafiz_abid@mentor.com>, <gdb-patches@sourceware.org>
Subject: About  New ARI warning Sun Mar 10 02:06:07 UTC 2013 in -D 2013-03-10-gmt
Date: Mon, 11 Mar 2013 14:38:00 -0000	[thread overview]
Message-ID: <007701ce1e66$0383f480$0a8bdd80$@muller@ics-cnrs.unistra.fr> (raw)
In-Reply-To: <1363003431.5561.0@abidh-ubunto1104>

  Thanks for the fast fix of this new ARI regression.

  Reading the comment of the rule shows that it is misleading,
because it says that we should not use && or ||,
but inside the script, it also looks == or != operators.

  I looked at the GNU coding standards,
and those in fact talk about any binary operator...
http://www.gnu.org/prep/standards/html_node/Formatting.html#Formatting

Should I:
1) modify the comment to also list != and ==
2) extend the rule to also check for other binary operators?


Pierre Muller 
as ARI maintainer....

> -----Message d'origine-----
> De : gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] De la part de Abid, Hafiz
> Envoyé : lundi 11 mars 2013 13:04
> À : gdb-patches@sourceware.org
> Objet : Re: New ARI warning Sun Mar 10 02:06:07 UTC 2013 in -D 2013-03-10-
> gmt
> 
> On 10/03/13 02:06:07, GDB Administrator wrote:
> > 623a624
> > > gdb/remote.c:11047: code: OP eol: Do not use &&, or || at the end
> > of a line
> > gdb/remote.c:11047:  if
> > (remote_protocol_packets[PACKET_QTBuffer_size].support !=
> >
> 
> Hi All,
> I noticed the above ARI warning. I will apply the following if there
> are no objections. I think it is obvious.
> 
> Regards,
> Abid
> 
> gdb/ChangeLog:
> 
> 	* remote.c (remote_set_trace_buffer_size): Move != operator
> 	to the start of next line to fix an ARI warning.
> 
> 
> diff --git a/gdb/remote.c b/gdb/remote.c
> index 8fc6b85..c4824e9 100644
> --- a/gdb/remote.c
> +++ b/gdb/remote.c
> @@ -11056,8 +11056,8 @@ remote_get_min_fast_tracepoint_insn_len (void)
>   static void
>   remote_set_trace_buffer_size (LONGEST val)
>   {
> -  if (remote_protocol_packets[PACKET_QTBuffer_size].support !=
> -      PACKET_DISABLE)
> +  if (remote_protocol_packets[PACKET_QTBuffer_size].support
> +      != PACKET_DISABLE)
>       {
>         struct remote_state *rs = get_remote_state ();
>         char *buf = rs->buf;


  parent reply	other threads:[~2013-03-11 14:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-10  2:06 GDB Administrator
2013-03-11 12:04 ` Abid, Hafiz
2013-03-11 12:09   ` Pedro Alves
2013-03-11 14:38   ` Pierre Muller [this message]
2013-03-11 17:58     ` About " Joel Brobecker
2013-03-13 14:41       ` [RFA] ARI: Extend binary operator at EOL checks (was: About New ARI warning Sun Mar 10 02:06:07 UTC 2013 in -D 2013-03-10-gmt) Pierre Muller
2013-03-20 15:52         ` Joel Brobecker
2013-03-20 16:42           ` Pierre Muller
2013-03-21  8:31             ` Pierre Muller
2013-03-21 12:01               ` GDB nightly build failure (was ARI: Extend binary operator at EOL checks ) Pierre Muller
2013-03-21 12:42                 ` Frank Ch. Eigler
2013-03-21 13:31                   ` Pierre Muller
2013-03-21 13:42                     ` Pierre Muller
2013-03-21 15:19               ` [RFA] ARI: Extend binary operator at EOL checks (was: About New ARI warning Sun Mar 10 02:06:07 UTC 2013 in -D 2013-03-10-gmt) Joel Brobecker

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='007701ce1e66$0383f480$0a8bdd80$@muller@ics-cnrs.unistra.fr' \
    --to=pierre.muller@ics-cnrs.unistra.fr \
    --cc=gdb-patches@sourceware.org \
    --cc=hafiz_abid@mentor.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