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: Jonathan Wakely <jwakely dot gcc at gmail dot com>
- To: "Bin.Cheng" <amker dot cheng at gmail dot com>
- Cc: "libstdc++" <libstdc++ at gcc dot gnu dot org>
- Date: Wed, 7 Aug 2013 12:08:32 +0100
- 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>
On 7 August 2013 12:05, Jonathan Wakely wrote:
>> FAIL: ext/headers.cc (test for excess errors)
>> Excess errors:
>> /home/build/work/gcc-build/arm-none-eabi/armv7-m/libstdc++-v3/include/arm-none-eabi/bits/gthr-default.h:37:30:
>> warning: non-static data member initializers only available with
>> -std=c++11 or -std=gnu++11 [enabled by default]
>> /home/build/work/gcc-build/arm-none-eabi/armv7-m/libstdc++-v3/include/arm-none-eabi/bits/gthr-default.h:37:30:
>> warning: non-static data member initializers only available with
>> -std=c++11 or -std=gnu++11 [enabled by default]
>>
>> The cases failed both on trunk and 4.8, but ok for 4.7.
>>
>> Any ideas? Thanks.
>
> There's not enough context to see what happened, the diagnostic is
> crap, only showing the macro not where it's used. The macro is not
> used as a non-static data member initializers except in C++11 mode, so
> I don't know how that could happen.
Ah actually that's not true, it's used in __mutex in ext/concurrence.h
So the next question is why you're getting a warning from system
headers, when it should be suppressed in libstdc++ headers. Are you
testing with -Wsystem-headers ?