Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: <gdb-patches@sourceware.org>
Subject: RE: New ARI warning Sat Mar 12 01:53:29 UTC 2011
Date: Sun, 13 Mar 2011 09:32:00 -0000	[thread overview]
Message-ID: <010f01cbe157$aebb5cb0$0c321610$@muller@ics-cnrs.unistra.fr> (raw)
In-Reply-To: <20110312015329.GA20179@sourceware.org>

  This is the consequence of the two new ARI rules I added:
http://sourceware.org/ml/gdb-patches/2011-03/msg00654.html

  As I just introduced these new rules,
I felt that it would be cheating to
use OBVIOUS rule as we normally do to fix 
a ARI regression...
  This is why I will submit shortly two patches
to remove all those new warnings.

Pierre Muller
as ARI maintainer.


> -----Message d'origine-----
> De : gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] De la part de GDB Administrator
> Envoyé : samedi 12 mars 2011 02:53
> À : gdb-patches@sourceware.org
> Objet : New ARI warning Sat Mar 12 01:53:29 UTC 2011
> 
> 76a77
> > gdb/breakpoint.c:11955: code: no parameter function: Function having
> no parameter should be declared with funcname (void).
> gdb/breakpoint.c:11955:all_tracepoints ()
> 259a261,262
> > gdb/f-exp.y:922: code: no parameter function: Function having no
> parameter should be declared with funcname (void).
> gdb/f-exp.y:922:match_string_literal ()
> > gdb/f-exp.y:954: code: no parameter function: Function having no
> parameter should be declared with funcname (void).
> gdb/f-exp.y:954:yylex ()
> 343a347
> > gdb/hppa-tdep.h:244: code: function call in first column: Function
> name in first column should be restricted to function implementation
> gdb/hppa-tdep.h:244:hppa_init_objfile_priv_data (struct objfile
> *objfile);
> 403a408
> > gdb/inferior.h:370: code: function call in first column: Function
> name in first column should be restricted to function implementation
> gdb/inferior.h:370:get_displaced_step_closure_by_addr (CORE_ADDR addr);
> 528a534
> > gdb/m2-exp.y:811: code: no parameter function: Function having no
> parameter should be declared with funcname (void).
> gdb/m2-exp.y:811:yylex ()
> 561a568,573
> > gdb/mep-tdep.c:848: code: no parameter function: Function having no
> parameter should be declared with funcname (void).
> gdb/mep-tdep.c:848:current_me_module ()
> > gdb/mep-tdep.c:871: code: no parameter function: Function having no
> parameter should be declared with funcname (void).
> gdb/mep-tdep.c:871:current_options ()
> > gdb/mep-tdep.c:888: code: no parameter function: Function having no
> parameter should be declared with funcname (void).
> gdb/mep-tdep.c:888:current_cop_data_bus_width ()
> > gdb/mep-tdep.c:897: code: no parameter function: Function having no
> parameter should be declared with funcname (void).
> gdb/mep-tdep.c:897:current_cr_names ()
> > gdb/mep-tdep.c:909: code: no parameter function: Function having no
> parameter should be declared with funcname (void).
> gdb/mep-tdep.c:909:current_cr_is_float ()
> > gdb/mep-tdep.c:921: code: no parameter function: Function having no
> parameter should be declared with funcname (void).
> gdb/mep-tdep.c:921:current_ccr_names ()
> 676a689,692
> > gdb/objc-exp.y:111: code: function call in first column: Function
> name in first column should be restricted to function implementation
> gdb/objc-exp.y:111:yyparse (void);
> > gdb/objc-exp.y:114: code: function call in first column: Function
> name in first column should be restricted to function implementation
> gdb/objc-exp.y:114:yylex (void);
> > gdb/objc-exp.y:117: code: function call in first column: Function
> name in first column should be restricted to function implementation
> gdb/objc-exp.y:117:yyerror (char *);
> > gdb/objc-exp.y:154: code: function call in first column: Function
> name in first column should be restricted to function implementation
> gdb/objc-exp.y:154:parse_number (char *, int, int, YYSTYPE *);
> 692a709
> > gdb/objc-exp.y:1221: code: no parameter function: Function having no
> parameter should be declared with funcname (void).
> gdb/objc-exp.y:1221:yylex ()
> 724a742,743
> > gdb/p-exp.y:121: code: function call in first column: Function name
> in first column should be restricted to function implementation
> gdb/p-exp.y:121:yyerror (char *);
> > gdb/p-exp.y:158: code: function call in first column: Function name
> in first column should be restricted to function implementation
> gdb/p-exp.y:158:parse_number (char *, int, int, YYSTYPE *);
> 733a753
> > gdb/p-exp.y:1123: code: no parameter function: Function having no
> parameter should be declared with funcname (void).
> gdb/p-exp.y:1123:yylex ()
> 831a852,855
> > gdb/python/py-evts.c:45: code: no parameter function: Function having
> no parameter should be declared with funcname (void).
> gdb/python/py-evts.c:45:gdbpy_initialize_py_events ()
> > gdb/python/py-prettyprint.c:397: code: no parameter function:
> Function having no parameter should be declared with funcname (void).
> gdb/python/py-prettyprint.c:397:push_dummy_python_frame ()
> > gdb/python/py-stopevent.h:32: code: function call in first column:
> Function name in first column should be restricted to function
> implementation
> gdb/python/py-stopevent.h:32:create_breakpoint_event_object (PyObject
> *breakpoint);
> > gdb/python/py-stopevent.h:35: code: function call in first column:
> Function name in first column should be restricted to function
> implementation
> gdb/python/py-stopevent.h:35:create_signal_event_object (enum
> target_signal stop_signal);
> 904a929
> > gdb/remote.c:3115: code: no parameter function: Function having no
> parameter should be declared with funcname (void).
> gdb/remote.c:3115:send_interrupt_sequence ()
> 1011a1037
> > gdb/solib-pa64.c:80: code: function call in first column: Function
> name in first column should be restricted to function implementation
> gdb/solib-pa64.c:80:read_dynamic_info (asection *dyninfo_sect,
> dld_cache_t *dld_cache_p);
> 1134a1161
> > gdb/tracepoint.c:221: code: no parameter function: Function having no
> parameter should be declared with funcname (void).
> gdb/tracepoint.c:221:current_trace_status ()
> 1234a1262
> > gdb/varobj.c:300: code: function call in first column: Function name
> in first column should be restricted to function implementation
> gdb/varobj.c:300:varobj_add_child (struct varobj *var, const char
> *name, struct value *value);
> 1236a1265
> > gdb/varobj.h:171: code: function call in first column: Function name
> in first column should be restricted to function implementation
> gdb/varobj.h:171:varobj_set_visualizer (struct varobj *var, const char
> *visualizer);
> 1296,1298d1324
> < gdb/xtensa-tdep.c:124: code: inline: Do not use the inline attribute;
> since the compiler generally ignores this, better algorithm selection
> is needed to improved performance
> gdb/xtensa-tdep.c:124:static inline int
> < gdb/xtensa-tdep.c:165: code: inline: Do not use the inline attribute;
> since the compiler generally ignores this, better algorithm selection
> is needed to improved performance
> gdb/xtensa-tdep.c:165:static inline unsigned long
> < gdb/xtensa-tdep.c:175: code: inline: Do not use the inline attribute;
> since the compiler generally ignores this, better algorithm selection
> is needed to improved performance
> gdb/xtensa-tdep.c:175:static inline void
> 1300d1325
> < gdb/xtensa-tdep.c:740: code: inline: Do not use the inline attribute;
> since the compiler generally ignores this, better algorithm selection
> is needed to improved performance
> gdb/xtensa-tdep.c:740:static inline


  reply	other threads:[~2011-03-13  8:21 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-12  2:17 GDB Administrator
2011-03-13  9:32 ` Pierre Muller [this message]
2011-03-13 10:24   ` [RFA] Fix ARI warning about function call in first column (was : New ARI warning Sat Mar 12 01:53:29 UTC 2011) Pierre Muller
2011-03-13 13:42   ` [RFA] Fix ARI warnings about function with no parameters ( " Pierre Muller
2011-03-14 16:03     ` Pierre Muller
2011-03-13 19:39   ` New ARI warning Sat Mar 12 01:53:29 UTC 2011 Eli Zaretskii
2011-03-14 11:26     ` Pierre Muller
2011-03-14 12:13       ` Eli Zaretskii
2011-03-14 12:34         ` Pedro Alves
2011-03-14 12:34           ` Eli Zaretskii
2011-03-14 12:49           ` Pierre Muller
2011-03-14 13:06             ` Eli Zaretskii
2011-03-14 12:51           ` Eli Zaretskii
2011-03-14 12:52             ` Pierre Muller
2011-03-14 13:16               ` Eli Zaretskii
2011-03-14 12:59             ` Pedro Alves
2011-03-14 13:27               ` Eli Zaretskii
2011-03-14 13:46                 ` Pedro Alves
2011-03-14 15:46                 ` Pierre Muller
2011-03-19 21:15                   ` Mark Kettenis
     [not found]   ` <18667.385276831$1300008680@news.gmane.org>
2011-03-14 15:54     ` [RFA] Fix ARI warning about function call in first column Tom Tromey
2011-03-14 16:46       ` [RFA-v2] " Pierre Muller
2011-03-14 17:02         ` Tom Tromey
     [not found]       ` <001401cbe261$5490ec40$fdb2c4c0$%muller@ics-cnrs.unistra.fr>
2011-03-14 17:17         ` Eli Zaretskii
2011-03-14 17:26           ` Pierre Muller
     [not found]           ` <10281.0550401502$1300122152@news.gmane.org>
2011-03-14 17:39             ` Tom Tromey
2011-03-15 12:19               ` [RFA] Fix formatting in " Pierre Muller
     [not found]               ` <45563.9187516228$1300186224@news.gmane.org>
2011-03-15 15:42                 ` Tom Tromey
2011-03-15 16:01                   ` Pierre Muller
     [not found]           ` <002001cbe269$85ed0e60$91c72b20$%muller@ics-cnrs.unistra.fr>
2011-03-14 21:26             ` Eli Zaretskii

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='010f01cbe157$aebb5cb0$0c321610$@muller@ics-cnrs.unistra.fr' \
    --to=pierre.muller@ics-cnrs.unistra.fr \
    --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