From: Joel Brobecker <brobecker@adacore.com>
To: Tom Tromey <tom@tromey.com>
Cc: GDB Administrator <gdbadmin@sourceware.org>, gdb-patches@sourceware.org
Subject: Re: New ARI warning Fri Jul 15 01:56:06 UTC 2016
Date: Fri, 15 Jul 2016 15:44:00 -0000 [thread overview]
Message-ID: <20160715154355.GA5353@adacore.com> (raw)
In-Reply-To: <8737nbo7ib.fsf@tromey.com>
> >> gdb/inflow.c:401: regression: ATTRIBUTE_UNUSED: Do not use
> >> ATTRIBUTE_UNUSED, do not bother (GDB is compiled with -Werror and,
> >> consequently, is not able to tolerate false warnings. Since
> >> -Wunused-param produces such warnings, neither that warning flag nor
> >> ATTRIBUTE_UNUSED are used by GDB
>
> I think it's time for this warning to go -- I don't recall the situation
> back when, but now there are multiple flags that might produce this
> warning, and I'd like gdb to enable at least two of them.
>
> I don't remember how to update ARI. Is it enough to edit
> contrib/ari/gdb_ari.sh?
I took a quick look, and it looks like not (yet). We have what
appears to be an older copy of that script, which we then use
to generate the ARI data. Switching over to the version from
the snapshot seems easy enough, but I'm going to be unavailable
in the next couple of days if something goes wrong.
What I would recommend, to start, is that Tom makes the modification.
I'll change our nightly scripts to use that version of the scripts,
and we'll see what happens.
We have the same issue with gdb_find.sh as well.
--
Joel
prev parent reply other threads:[~2016-07-15 15:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-15 1:56 GDB Administrator
2016-07-15 4:22 ` Tom Tromey
2016-07-15 11:57 ` Yao Qi
2016-07-15 15:44 ` Joel Brobecker [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=20160715154355.GA5353@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=gdbadmin@sourceware.org \
--cc=tom@tromey.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).