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: Florian Weimer <fweimer at redhat dot com>
- Cc: "libstdc++" <libstdc++ at gcc dot gnu dot org>
- Date: Wed, 7 Aug 2013 12:28:58 +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> <52022AA0 dot 4030601 at redhat dot com> <CAH6eHdQ1WPFQu2kQ2U8OWFk7A8AvvSRf6fj11Xb9oREge+YBVA at mail dot gmail dot com> <CAH6eHdRWHPcMiHR6wrOFh4RvazkNDyhqchbcUPjyqeg5=bi17Q at mail dot gmail dot com>
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.