This is the mail archive of the libstdc++@gcc.gnu.org mailing list for the libstdc++ project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: libstdc++ test case ext/headers.cc failed on arm-none-eabi


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.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]