From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 99861 invoked by alias); 17 Sep 2015 05:07:52 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 99848 invoked by uid 89); 17 Sep 2015 05:07:51 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_SOFTFAIL autolearn=no version=3.3.2 X-HELO: mtaout27.012.net.il Received: from mtaout27.012.net.il (HELO mtaout27.012.net.il) (80.179.55.183) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 17 Sep 2015 05:07:48 +0000 Received: from conversion-daemon.mtaout27.012.net.il by mtaout27.012.net.il (HyperSendmail v2007.08) id <0NUT00I001WQ5L00@mtaout27.012.net.il> for gdb-patches@sourceware.org; Thu, 17 Sep 2015 08:04:14 +0300 (IDT) Received: from HOME-C4E4A596F7 ([84.94.185.246]) by mtaout27.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0NUT0092D2323KA0@mtaout27.012.net.il>; Thu, 17 Sep 2015 08:04:14 +0300 (IDT) Date: Thu, 17 Sep 2015 05:07:00 -0000 From: Eli Zaretskii Subject: Re: [patch, testsuite] check for UTF-32 target wide charset support in gdb.base/wchar.exp In-reply-to: <55FA325D.1020207@codesourcery.com> To: Sandra Loosemore Cc: gdb-patches@sourceware.org Reply-to: Eli Zaretskii Message-id: <8361397hwd.fsf@gnu.org> References: <55FA325D.1020207@codesourcery.com> X-IsSubscribed: yes X-SW-Source: 2015-09/txt/msg00394.txt.bz2 > Date: Wed, 16 Sep 2015 21:24:13 -0600 > From: Sandra Loosemore > > 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?