This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
dg-error vs. i18n?
- From: Dave Korn <dave dot korn dot cygwin at googlemail dot com>
- To: "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
- Date: Sat, 24 Oct 2009 00:01:56 +0100
- Subject: dg-error vs. i18n?
Hi everyone,
Sorry for posting a dumb question, but it's not my strongest area: now that
cygwin is handling i18n and unicode and "all that stuff", I started seeing a
whole slew of test failures, e.g.:
> FAIL: g++.dg/debug/pr22514.C (test for errors, line 12)
> FAIL: g++.dg/debug/pr22514.C (test for excess errors)
> Excess errors:
> /gnu/gcc/releases/4.3.4-2/gcc4-4.3.4-2/src/gcc-4.3.4/gcc/testsuite/g++.dg/debug/pr22514.C:12:
> error: expected unqualified-id before ‘}’ token
The reason appears to be because the testcase has single-quotes in the regex
pattern:
>> $ cat g++.dg/debug/pr22514.C -n
>> 1 /* { dg-do compile } */
>> 2 namespace s
>> 3 {
>> 4 template <int> struct _List_base
>> 5 {
>> 6 int _M_impl;
>> 7 };
>> 8 template<int i> struct list : _List_base<i>
>> 9 {
>> 10 using _List_base<i>::_M_impl;
>> 11 }
>> 12 } /* { dg-error "expected unqualified-id before '\}'" } */
>> 13 s::list<1> OutputModuleListType;
... where the actual compiler outputs those fancy left- and right-facing
quotes. It will probably go away if I set LC_ALL=c or something like that,
but is dg-error meant to be insensitive to this kind of transformation, or
would it be best if dg-error test patterns didn't include any kind of quote
chars that might get i14ed?
cheers,
DaveK