From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1642 invoked by alias); 17 Sep 2009 10:25:04 -0000 Received: (qmail 1608 invoked by uid 22791); 17 Sep 2009 10:25:02 -0000 X-SWARE-Spam-Status: No, hits=-2.3 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (65.74.133.4) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 17 Sep 2009 10:24:57 +0000 Received: (qmail 15448 invoked from network); 17 Sep 2009 10:24:55 -0000 Received: from unknown (HELO orlando) (pedro@127.0.0.2) by mail.codesourcery.com with ESMTPA; 17 Sep 2009 10:24:55 -0000 From: Pedro Alves To: gdb-patches@sourceware.org, Eli Zaretskii Subject: Re: Default target wide character set Date: Thu, 17 Sep 2009 10:25:00 -0000 User-Agent: KMail/1.9.10 Cc: tromey@redhat.com, alexeyf@opera.com References: <200909162011.19409.pedro@codesourcery.com> <83ws3ywrl3.fsf@gnu.org> In-Reply-To: <83ws3ywrl3.fsf@gnu.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200909171125.11172.pedro@codesourcery.com> X-IsSubscribed: yes 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 X-SW-Source: 2009-09/txt/msg00561.txt.bz2 On Wednesday 16 September 2009 21:40:56, Eli Zaretskii wrote: > > From: Pedro Alves > > Date: Wed, 16 Sep 2009 20:11:18 +0100 > > Cc: "Alexey Feldgendler" > > > > Something like that would also be useful for Windows targets, and would > > address PR9996: > > > > http://sourceware.org/bugzilla/show_bug.cgi?id=9996 > > Are you sure this PR still holds with the newer Cygwin 1.7? does > Cygwin still use 2-byte wchar_t? I'm not 100% sure, but I'm 99.9(9)% sure, but only because I didn't take the trouble to confirm it myself. Why wouldn't it? Given that 2-byte WCHAR is what Windows NT uses internally to store and handle strings, and hence what is passed back and forth between Cygwin and the NT and Win32 APIs Cygwin uses to do its business, switching away from 2-byte wchar_t on Cygwin doesn't sound like a bad idea to me. -- Pedro Alves