From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/7079 Path: news.gmane.org!not-for-mail From: Sergey Dmitrouk Newsgroups: gmane.linux.lib.musl.general Subject: Re: wchar_t and -fshort-wchar Date: Fri, 20 Feb 2015 08:53:02 +0200 Message-ID: <20150220065302.GA1364@zx-spectrum> References: <20150218105337.GA8567@zx-spectrum> <20150220042602.GQ23507@brightrain.aerifal.cx> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Trace: ger.gmane.org 1424415194 12869 80.91.229.3 (20 Feb 2015 06:53:14 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 20 Feb 2015 06:53:14 +0000 (UTC) Cc: "musl@lists.openwall.com" To: Rich Felker Original-X-From: musl-return-7092-gllmg-musl=m.gmane.org@lists.openwall.com Fri Feb 20 07:53:14 2015 Return-path: Envelope-to: gllmg-musl@m.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1YOhSb-00077K-8i for gllmg-musl@m.gmane.org; Fri, 20 Feb 2015 07:53:13 +0100 Original-Received: (qmail 3665 invoked by uid 550); 20 Feb 2015 06:53:11 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Original-Received: (qmail 3619 invoked from network); 20 Feb 2015 06:53:08 -0000 Content-Disposition: inline In-Reply-To: <20150220042602.GQ23507@brightrain.aerifal.cx> Xref: news.gmane.org gmane.linux.lib.musl.general:7079 Archived-At: On Thu, Feb 19, 2015 at 08:26:02PM -0800, Rich Felker wrote: > musl does not support configurations with under-sized definitions of > types like 16-bit wchar_t or 32-bit off_t. Only the sizes that can > represent the full range of values are supported. musl does however > have the C11 uchar.h functions which can operate on char16_t, so you > could use char16_t and the corresponding c16 conversion functions > instead of the wc versions if that helps. What are you trying to > achieve? Nothing particular, -fshort-wchar is dictated by some compatibility requirements, which are probably caused by building things on Windows, where sizeof(wchar_t) usually equals to 2. Maybe the flag will go away later, if not, will try using uchar.h in case there will be a need, thanks for the pointer. -- Sergey