From: Eli Zaretskii <eliz@gnu.org>
To: Doug Evans <xdje42@gmail.com>
Cc: 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: Thu, 17 Sep 2015 05:10:00 -0000 [thread overview]
Message-ID: <834mit7hrm.fsf@gnu.org> (raw)
In-Reply-To: <m3k2rpsm4p.fsf@sspiff.org>
> From: Doug Evans <xdje42@gmail.com>
> Cc: gdb-patches <gdb-patches@sourceware.org>
> Date: Wed, 16 Sep 2015 21:30:46 -0700
>
> #undef GDB_DEFAULT_HOST_CHARSET
> #define GDB_DEFAULT_HOST_CHARSET "ISO-8859-1"
> #define GDB_DEFAULT_TARGET_CHARSET "ISO-8859-1"
> #define GDB_DEFAULT_TARGET_WIDE_CHARSET "ISO-8859-1" <<<<
>
> How reasonable is it to enhance the PHONY_ICONV support so that
> it handles this better?
You mean, have functions like strlen and strcat handle 32-bit wchar_t
strings? Not reasonable.
> I see it already tries to provide some minimal functionality:
>
> static iconv_t
> phony_iconv_open (const char *to, const char *from)
> {
> /* We allow conversions from UTF-32BE, wchar_t, and the host charset.
> We allow conversions to wchar_t and the host charset. */
> if (strcmp (from, "UTF-32BE") && strcmp (from, "wchar_t")
> && strcmp (from, GDB_DEFAULT_HOST_CHARSET))
> return -1;
> if (strcmp (to, "wchar_t") && strcmp (to, GDB_DEFAULT_HOST_CHARSET))
> return -1;
>
> /* Return 1 if we are converting from UTF-32BE, 0 otherwise. This is
> used as a flag in calls to iconv. */
> return !strcmp (from, "UTF-32BE");
> }
>
> I don't know, off hand, why big endian is supported and not little endian.
Supported by whom?
next prev parent reply other threads:[~2015-09-17 5:10 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 [this message]
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
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=834mit7hrm.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=sandra@codesourcery.com \
--cc=xdje42@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