From: Keith Seitz <keiths@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>, gdb-patches@sourceware.org
Subject: Re: New ARI warning Wed Aug 12 01:53:55 UTC 2015
Date: Fri, 14 Aug 2015 18:12:00 -0000 [thread overview]
Message-ID: <55CE2F9D.4030001@redhat.com> (raw)
In-Reply-To: <20150814180556.GN22245@adacore.com>
On 08/14/2015 11:05 AM, Joel Brobecker wrote:
> I'm wondering what other people think of these. On the one hand,
> I'm pretty sure the ARI check is too simplistic and N/A for
> this code. On the other hand, I'd like to think that our long
> term goal/hope is to have a clean ARI report someday.
>
> We could tell the ARI that these are OK by adding explicit ARI:
> markers, but it seems to me that it'd be just as simple to change
> the name of the parameter for each macro.
I have it on my plate to address this after BuildBot stops harassing me. :-)
My inclination was to fix gdb_ari.sh to recognize this, but I'm just as
happy to simply rename the parameter to "P". [It's a lot less work, too!]
Keith
next prev parent reply other threads:[~2015-08-14 18:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-12 1:53 GDB Administrator
2015-08-14 18:06 ` Joel Brobecker
2015-08-14 18:12 ` Keith Seitz [this message]
2015-08-14 18:32 ` Joel Brobecker
2015-08-14 22:19 ` Keith Seitz
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=55CE2F9D.4030001@redhat.com \
--to=keiths@redhat.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