From: Pedro Alves <palves@redhat.com>
To: Yao Qi <yao@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 6/7] Include wchar.h and wctype.h unconditionally
Date: Fri, 21 Nov 2014 12:49:00 -0000 [thread overview]
Message-ID: <546F34BA.20809@redhat.com> (raw)
In-Reply-To: <1416057612-16155-7-git-send-email-yao@codesourcery.com>
On 11/15/2014 01:20 PM, Yao Qi wrote:
> As gnulib modules wchar and wctype is imported, we can include wchar.h
> and wctype.h unconditionally. This patch is also to remove HAVE_WCHAR_H
> check.
>
> gdb:
>
> 2014-11-15 Yao Qi <yao@codesourcery.com>
>
> * gdb_wchar.h: Include wchar.h and wctype.h.
> [HAVE_ICONV && HAVE_BTOWC]: Don't check HAVE_WCHAR_T and don't
> include wchar.h and wctype.h.
> Don't check HAVE_WCHAR_H.
> ---
> gdb/gdb_wchar.h | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/gdb/gdb_wchar.h b/gdb/gdb_wchar.h
> index f88673b..c7a0f1e 100644
> --- a/gdb/gdb_wchar.h
> +++ b/gdb/gdb_wchar.h
> @@ -49,18 +49,18 @@
> #define PHONY_ICONV
> #endif
>
> +#include <wchar.h>
> +#include <wctype.h>
> +
> /* We use "btowc" as a sentinel to detect functioning wchar_t support.
> We check for either __STDC_ISO_10646__ or a new-enough libiconv in
> order to ensure we can convert to and from wchar_t. We choose
> libiconv version 0x108 because it is the first version with
> iconvlist. */
> -#if defined (HAVE_ICONV) && defined (HAVE_WCHAR_H) && defined (HAVE_BTOWC) \
> +#if defined (HAVE_ICONV) && defined (HAVE_BTOWC) \
> && (defined (__STDC_ISO_10646__) \
> || (defined (_LIBICONV_VERSION) && _LIBICONV_VERSION >= 0x108))
>
> -#include <wchar.h>
> -#include <wctype.h>
> -
> typedef wchar_t gdb_wchar_t;
> typedef wint_t gdb_wint_t;
>
> @@ -94,7 +94,7 @@ const char *intermediate_encoding (void);
>
> /* If we got here and have wchar_t support, we might be on a system
> with some problem. So, we just disable everything. */
> -#if defined (HAVE_WCHAR_H) && defined (HAVE_BTOWC)
> +#if defined (HAVE_BTOWC)
> #define PHONY_ICONV
> #endif
It's hard to reason about all the modes supported here, but
I think this is OK. Seems like the comment above about wchar_t
support should be updated though.
(I wonder whether if we pulled in the gnulib btowc module, we could
get rid of at least some of this fallback stuff. We're already
pulling in mbrtowc...)
Thanks,
Pedro Alves
next prev parent reply other threads:[~2014-11-21 12:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-15 13:20 [PATCH 0/7] Import needed gnulib modules explicitly Yao Qi
2014-11-15 13:20 ` [PATCH 4/7] Import memchr explicitly Yao Qi
2014-11-15 13:20 ` [PATCH 7/7] Import errno explicitly Yao Qi
2014-11-15 13:20 ` [PATCH 2/7] Import alloca explicitly Yao Qi
2014-11-15 13:20 ` [PATCH 1/7] Make IMPORTED_GNULIB_MODULES in alphabetical order Yao Qi
2014-11-21 12:21 ` Pedro Alves
2014-11-15 13:20 ` [PATCH 6/7] Include wchar.h and wctype.h unconditionally Yao Qi
2014-11-21 12:49 ` Pedro Alves [this message]
2014-11-21 13:22 ` Yao Qi
2014-11-15 13:20 ` [PATCH 5/7] Import wchar and wctype-h explicitly Yao Qi
2014-11-15 13:20 ` [PATCH 3/7] Include alloca.h unconditionally Yao Qi
2014-11-21 12:21 ` Pedro Alves
2014-11-21 13:05 ` Yao Qi
2014-11-21 13:17 ` Pedro Alves
2014-11-21 11:54 ` [PATCH 0/7] Import needed gnulib modules explicitly Yao Qi
2014-11-21 12:50 ` Pedro Alves
2014-11-21 14:06 ` Yao Qi
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=546F34BA.20809@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=yao@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