From: Doug Evans <xdje42@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Sandra Loosemore <sandra@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: [patch, testsuite] check for UTF-32 target wide charset support in gdb.base/wchar.exp
Date: Fri, 18 Sep 2015 04:41:00 -0000 [thread overview]
Message-ID: <m3wpvoqr0v.fsf@sspiff.org> (raw)
In-Reply-To: <8361397hwd.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 17 Sep 2015 08:07:46 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> Date: Wed, 16 Sep 2015 21:24:13 -0600
>> From: Sandra Loosemore <sandra@codesourcery.com>
>>
>> If GDB is configured without ICONV support, the target wide charset
>> defaults to "ISO-8859-1" (which isn't even a wide charset), and all the
>> wide strings in this test print as gibberish. Otherwise, GDB seems to
>> think the default is "auto; currently UTF-32", so let's make the
>> dependency on UTF-32 explicit here and bail out if it's not available.
>
> Why UTF-32, hard-coded? Why not allow also UTF-16, for example?
Because this is the case of no iconv support and thus gdb is supplying its own
minimal version. No point in supporting anything unwarranted.
If a compelling case arises for UTF-16 we can cross that bridge
when we get to it.
prev parent reply other threads:[~2015-09-18 4:41 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
2015-09-18 4:48 ` Doug Evans
2015-09-29 13:50 ` Pedro Alves
2015-09-18 4:41 ` Doug Evans [this message]
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=m3wpvoqr0v.fsf@sspiff.org \
--to=xdje42@gmail.com \
--cc=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