From: Pedro Alves <palves@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [testsuite patch] Fix C++11 compilation failure for gdb.cp/m-static.exp
Date: Thu, 15 Sep 2016 12:22:00 -0000 [thread overview]
Message-ID: <ad9bde03-2d84-402a-5dd2-daaed5d05427@redhat.com> (raw)
In-Reply-To: <20160911142248.GA12817@host1.jankratochvil.net>
On 09/11/2016 03:22 PM, Jan Kratochvil wrote:
>
> After the fix out of the 4 combinations above only this one remains non-empty:
>
> clang++:
> In file included from /home/jkratoch/redhat/gdb-clean/gdb/testsuite/gdb.cp/m-static.cc:79:
> /home/jkratoch/redhat/gdb-clean/gdb/testsuite/gdb.cp/m-static.h:9:22: warning: in-class initializer for static data member of type 'const float' is a GNU extension [-Wgnu-static-float-init]
> static const float somewhere = 3.14159;
> ^ ~~~~~~~
> 1 warning generated.
>
Did you try moving the initialization to the .cc file? Like:
const float gnu_obj_4::somewhere = 3.14159;
Did you find a reason to not do that?
Thanks,
Pedro Alves
next prev parent reply other threads:[~2016-09-15 12:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-11 14:22 Jan Kratochvil
2016-09-15 12:22 ` Pedro Alves [this message]
2016-09-15 12:34 ` Jan Kratochvil
2016-09-15 13:11 ` Pedro Alves
2016-09-15 21:47 ` [commit] " Jan Kratochvil
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=ad9bde03-2d84-402a-5dd2-daaed5d05427@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.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