From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22133 invoked by alias); 29 Sep 2015 13:50:37 -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 22067 invoked by uid 89); 29 Sep 2015 13:50:36 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,T_RP_MATCHES_RCVD autolearn=ham version=3.3.2 X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Tue, 29 Sep 2015 13:50:31 +0000 Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) by mx1.redhat.com (Postfix) with ESMTPS id A0E9DAC84C; Tue, 29 Sep 2015 13:50:29 +0000 (UTC) Received: from [127.0.0.1] (ovpn01.gateway.prod.ext.ams2.redhat.com [10.39.146.11]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id t8TDoRNA015301; Tue, 29 Sep 2015 09:50:28 -0400 Message-ID: <560A9723.3050108@redhat.com> Date: Tue, 29 Sep 2015 13:50:00 -0000 From: Pedro Alves User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: Doug Evans , Sandra Loosemore CC: Eli Zaretskii , gdb-patches@sourceware.org Subject: Re: [patch, testsuite] check for UTF-32 target wide charset support in gdb.base/wchar.exp References: <55FA325D.1020207@codesourcery.com> <8361397hwd.fsf@gnu.org> <55FA4CB5.4010802@codesourcery.com> In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-SW-Source: 2015-09/txt/msg00633.txt.bz2 On 09/18/2015 05:47 AM, Doug Evans wrote: > The question I have is what's the intent behind PHONY_ICONV? > [The fact that it apparently tries to provide some minimal wide char > support but defines GDB_DEFAULT_TARGET_WIDE_CHARSET as "ISO-8859-1" > seems like a bug to me.] > > Is it intended that it provide some minimal wide char support? I recall the feature being submitted and the follow up Solaris fixes, but I wasn't the one doing the work, so I'm not 100% sure of anything, but I believe the intention is to punt on wide char support with the least extra code possible. That seems to be what the original submission suggests as well: https://sourceware.org/ml/gdb-patches/2009-01/msg00533.html https://sourceware.org/ml/gdb-patches/2009-03/msg00420.html along with the comments in mails around the follow up Solaris fixes: https://www.sourceware.org/ml/gdb-patches/2010-08/msg00339.html Thanks, Pedro Alves