From: Tom Tromey <tom@tromey.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: brobecker@adacore.com, gdb-patches@sourceware.org
Subject: Re: GDB 8.1.90 available for testing
Date: Sun, 29 Jul 2018 18:43:00 -0000 [thread overview]
Message-ID: <87tvohopcc.fsf@tromey.com> (raw)
In-Reply-To: <837eleu5q7.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 29 Jul 2018 05:37:52 +0300")
>>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:
>> CXX symfile.o
>> symfile.c: In function 'void set_objfile_default_section_offset(objfile*, const section_addr_info&, CORE_ADDR)':
>> symfile.c:2114:14: warning: types may not be defined in a for-range-declaration
>> for (const struct other_sections *objf_sect : objf_addrs_sorted)
>> ^~~~~~
>>
>> The first two I saw in GDB 8.1 and reported back in January. I
>> believe the conclusion was that we disregard these warnings?
>>
>> But what about the 3rd one?
I think this is a gcc bug. This looks related:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79566
Simon occasionally fixes these by removing the 'struct' keyword.
This seems fine since it isn't really inconvenient and people may be
using the buggy versions of gcc.
This particular spot was fixed on git master in revision ff27d0737ef0.
I think it would be fine to cherry-pick that to the branch.
Tom
next prev parent reply other threads:[~2018-07-29 18:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-04 16:32 Joel Brobecker
2018-07-18 16:13 ` Eli Zaretskii
2018-07-19 14:37 ` Tom Tromey
2018-07-19 14:48 ` Eli Zaretskii
2018-07-29 2:37 ` Eli Zaretskii
2018-07-29 18:43 ` Tom Tromey [this message]
2018-07-31 16:58 ` 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=87tvohopcc.fsf@tromey.com \
--to=tom@tromey.com \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--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