This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: libstdc++ test case ext/headers.cc failed on arm-none-eabi
- From: "Bin.Cheng" <amker dot cheng at gmail dot com>
- To: Paolo Carlini <paolo dot carlini at oracle dot com>
- Cc: Jonathan Wakely <jwakely dot gcc at gmail dot com>, Florian Weimer <fweimer at redhat dot com>, "libstdc++" <libstdc++ at gcc dot gnu dot org>
- Date: Wed, 7 Aug 2013 21:34:05 +0800
- Subject: Re: libstdc++ test case ext/headers.cc failed on arm-none-eabi
- References: <CAHFci282xzqC07Nu03Az+VuwOjm2b3gzDr4Oty-OBW6NKa5ekg at mail dot gmail dot com> <CAH6eHdSqQmRcY8ZXKzQSHAm0+K6N9ztqmj7-o8pdNBG8WvT3NA at mail dot gmail dot com> <52022AA0 dot 4030601 at redhat dot com> <CAH6eHdQ1WPFQu2kQ2U8OWFk7A8AvvSRf6fj11Xb9oREge+YBVA at mail dot gmail dot com> <CAH6eHdRWHPcMiHR6wrOFh4RvazkNDyhqchbcUPjyqeg5=bi17Q at mail dot gmail dot com> <CAH6eHdQ97ZCG=sYCHvV58TvuBGwpNokKXBegc8POFnPNwY2GwA at mail dot gmail dot com> <52023215 dot 7090203 at oracle dot com>
On Wed, Aug 7, 2013 at 7:40 PM, Paolo Carlini <paolo.carlini@oracle.com> wrote:
> Hi,
>
>
> On 08/07/2013 01:28 PM, Jonathan Wakely wrote:
>>
>> I don't understand why the error location is given as the macro
>> definition, rather than where the non-static data member initializer
>> is actually used. The fact the initializer happens to be a macro
>> shouldn't matter, the warnng should indicate where the initializer is
>> used.
>
> I suspect this is a known issue. Related to the fact that literals don't
> have locations? Eg: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52718
>
> Paolo.
Thanks all of you for helping.
Since I know little about c++, here comes more questions:
1) for the warning message:
g.h:2:14: warning: non-static data member initializers only available
with -std=c++11 or -std=gnu++11 [enabled by default]
#define INIT 0
^
What does the "[enabled by default]" mean? If "-std=gnu++11" is
enabled by default, why gcc gives this warning message then?
2) The case works for x86 regression test, could this be a target (or
target testing setup) specific problem? What kind of imformation
should I provide to identify the issue?
3) According to the explanation, this possibly reveals two issues, one
for the warning message itself, and the other for the inaccurate
warning message, right?
Thanks very much.
--
Best Regards.