From: Simon Marchi <simon.marchi@polymtl.ca>
To: Steve Ellcey <sellcey@caviumnetworks.com>
Cc: gdb@sourceware.org
Subject: Re: GDB build failure when using latest (ToT) GCC
Date: Mon, 27 Feb 2017 19:57:00 -0000 [thread overview]
Message-ID: <826291c6a32e75be84c1582f7205b282@polymtl.ca> (raw)
In-Reply-To: <1488225059.2866.220.camel@caviumnetworks.com>
On 2017-02-27 14:50, Steve Ellcey wrote:
> I am building the ToT gdb with a ToT GCC and getting this error:
>
> ../../../src/binutils-gdb/gdb/remote.c: In function âint
> remote_add_target_side_
> condition(gdbarch*, bp_target_info*, char*, char*)â:
> ../../../src/binutils-gdb/gdb/remote.c:9668:8: error: types may not be
> defined i
> n a for-range-declaration [-fpermissive]
> Â Â Â for (struct agent_expr *aexpr : bp_tgt->conditions)
> Â Â Â Â Â Â Â Â ^~~~~~
> Makefile:1898: recipe for target 'remote.o' failed
>
>
> Does anyone know how to change this code so that GCC will not complain?
> I am not familiar with C++ for ranges. I get a bunch of warnings too,
> but this
> is a hard error that stops my compilation.  Yes, I can use -fpermissive
> but I
> would rather not and this will need to be fixed when GCC 7.X comes out.
Hi Steve,
I indeed broke the build for recent GCCs in
Use range-based for loop in remote_add_target_side_condition
8362122330c97c8c4a15da4e7ba8aa29f0c11157
and fixed it right after with
Remove struct keyword from range-based for loop
d538e36decd5628c084dbd5a7de13719b8b92121
I am still using an ancient 4.8 GCC, so I did not see it, but Sergio's
buildbot informed me within a few minutes. Let's just pretend it was a
test for the bot :). Sorry about the inconvenience and thanks for being
alert.
Simon
next prev parent reply other threads:[~2017-02-27 19:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-27 19:51 Steve Ellcey
2017-02-27 19:57 ` Simon Marchi [this message]
2017-02-27 21:11 ` Steve Ellcey
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=826291c6a32e75be84c1582f7205b282@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=gdb@sourceware.org \
--cc=sellcey@caviumnetworks.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