From: Joel Brobecker <brobecker@adacore.com>
To: Pierre Muller <pierre.muller@ics-cnrs.unistra.fr>
Cc: gdb-patches@sourceware.org
Subject: Re: New ARI warning Thu Apr 18 01:51:12 UTC 2013 in -D 2013-04-18-gmt
Date: Fri, 19 Apr 2013 14:31:00 -0000 [thread overview]
Message-ID: <20130419070129.GJ3525@adacore.com> (raw)
In-Reply-To: <001b01ce3c82$d36e2870$7a4a7950$@muller@ics-cnrs.unistra.fr>
On Fri, Apr 19, 2013 at 12:19:41AM +0200, Pierre Muller wrote:
>
>
> > -----Message d'origine-----
> > De : gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> > owner@sourceware.org] De la part de Joel Brobecker
> > Envoyé : jeudi 18 avril 2013 17:17
> > ÃÂ : GDB Administrator
> > Cc : gdb-patches@sourceware.org
> > Objet : Re: New ARI warning Thu Apr 18 01:51:12 UTC 2013 in -D 2013-04-18-
> > gmt
> >
> > > > gdb/dwarf2read.c:17927: code: editCase function: Function name starts
> > lower case but has uppercased letters.
> > > gdb/dwarf2read.c:17927:get_DW_AT_signature_type (struct die_info *die,
> > struct attribute *attr, struct dwarf2_cu *cu)
> >
> > Let's add an ARI marker to accept this as a valid exception...
> I agree in principle,
> but the problem is that to avoid the warning you should add
> /* ARI: editCase */ comment...
> And the natural position to insert such comment would
> be after the closing brace of the parameter list.
I was actually thinking of writing it like so:
get_DW_AT_signature_type /* ARI: editCase */
(struct die_info *die, struct attribute *attr,
struct dwarf2_cu *cu)
{
}
Not ideal, but I do not think it would be the first time that
the arguments start on the line following the function name...
--
Joel
next prev parent reply other threads:[~2013-04-19 7:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-18 16:02 GDB Administrator
2013-04-19 14:27 ` Joel Brobecker
2013-04-19 14:29 ` Pierre Muller
2013-04-19 14:31 ` Joel Brobecker [this message]
2013-04-29 14:47 ` [commit] Add ARI marker to get_DW_AT_signature_type Joel Brobecker
2013-04-29 15:30 ` Pierre Muller
2013-04-29 15:30 ` Joel Brobecker
2013-04-29 17:19 ` Pierre Muller
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=20130419070129.GJ3525@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=pierre.muller@ics-cnrs.unistra.fr \
/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