From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Dave Korn <dave.korn.cygwin@googlemail.com>
Cc: Richard Guenther <richard.guenther@gmail.com>,
"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: dg-error vs. i18n?
Date: Sun, 25 Oct 2009 18:42:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.0910251733490.3671@digraph.polyomino.org.uk> (raw)
In-Reply-To: <4AE3616C.9000007@gmail.com>
On Sat, 24 Oct 2009, Dave Korn wrote:
> Joseph S. Myers wrote:
> > On Sat, 24 Oct 2009, Richard Guenther wrote:
> >
> >> The testsuite should run with C locale.
> >
> > Unfortunately it appears there are now some systems where C no longer
> > implies ASCII, causing problems for predictability of output.
>
> I was asked about this on another list: by "some systems", do you mean any
> other than Cygwin? Are you specifically aware of any e.g. linux distros that
> default to say UTF-8 in the C locale, or were you just making a general
> statement since the Cygwin case proves that there "exists at least one" such
> system?
It was stated on #gcc on 12 August that AIX 5.3 returns "ISO8859-1" from
nl_langinfo (CODESET) in the C locale, which also causes problems for
testcases that are making assertions about GCC's English-language,
ASCII-charset output.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2009-10-25 17:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-23 23:04 Dave Korn
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 [this message]
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=Pine.LNX.4.64.0910251733490.3671@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=dave.korn.cygwin@googlemail.com \
--cc=gcc@gcc.gnu.org \
--cc=richard.guenther@gmail.com \
/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).