From: Dave Korn <dave.korn.cygwin@googlemail.com>
To: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: dg-error vs. i18n?
Date: Fri, 23 Oct 2009 23:04:00 -0000 [thread overview]
Message-ID: <4AE235E4.2060005@gmail.com> (raw)
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
next reply other threads:[~2009-10-23 22:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-23 23:04 Dave Korn [this message]
2009-10-23 23:08 ` Richard Guenther
2009-10-24 0:04 ` Joseph S. Myers
2009-10-24 2:28 ` Dave Korn
2009-10-24 5:06 ` Charles Wilson
2009-10-25 11:19 ` Dave Korn
2009-10-25 18:42 ` Joseph S. Myers
2009-10-23 23:19 ` Andrew Pinski
2009-10-24 1:28 ` Dave Korn
2009-10-24 20:05 ` Andreas Schwab
2009-10-25 11:08 ` Charles Wilson
2009-10-27 15:49 ` Eric Blake
2009-10-27 20:18 ` Dave Korn
2009-10-24 15:17 ` Andreas Schwab
2009-10-28 11:30 Ross Ridge
2009-10-28 17:34 ` Joseph S. Myers
2009-10-28 18:59 Ross Ridge
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4AE235E4.2060005@gmail.com \
--to=dave.korn.cygwin@googlemail.com \
--cc=gcc@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).