From: Eli Zaretskii <eliz@gnu.org>
To: Sandra Loosemore <sandra@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch, testsuite] check for UTF-32 target wide charset support in gdb.base/wchar.exp
Date: Thu, 17 Sep 2015 05:59:00 -0000 [thread overview]
Message-ID: <831tdx7fhh.fsf@gnu.org> (raw)
In-Reply-To: <55FA4CB5.4010802@codesourcery.com>
> Date: Wed, 16 Sep 2015 23:16:37 -0600
> From: Sandra Loosemore <sandra@codesourcery.com>
> CC: <gdb-patches@sourceware.org>
>
> If I'm confused and the default charset might not always be UTF-32 if
> ICONV is present, how about changing the testcase to bail if it sees the
> default wide charset is ISO-8859-1? That means either ICONV is not
> present or GDB's default is otherwise wrongly configured.
If the test makes no sense without ICONV, I think it indeed will be
better to skip it.
next prev parent reply other threads:[~2015-09-17 5:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-17 3:25 Sandra Loosemore
2015-09-17 4:31 ` Doug Evans
2015-09-17 5:10 ` Eli Zaretskii
2015-09-18 4:38 ` Doug Evans
2015-09-17 5:07 ` Eli Zaretskii
2015-09-17 5:17 ` Sandra Loosemore
2015-09-17 5:59 ` Eli Zaretskii [this message]
2015-09-18 4:48 ` Doug Evans
2015-09-29 13:50 ` Pedro Alves
2015-09-18 4:41 ` Doug Evans
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=831tdx7fhh.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=sandra@codesourcery.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