From owner-freebsd-bugs@FreeBSD.ORG Sat Feb 9 17:53:02 2013 Return-Path: Delivered-To: freebsd-bugs@FreeBSD.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 9A68E65E; Sat, 9 Feb 2013 17:53:02 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from tensor.andric.com (tensor.andric.com [87.251.56.140]) by mx1.freebsd.org (Postfix) with ESMTP id 5EC2B6E0; Sat, 9 Feb 2013 17:52:58 +0000 (UTC) Received: from [IPv6:2001:7b8:3a7:0:204:4bff:fe01:de8a] (spaceball.andric.com [IPv6:2001:7b8:3a7:0:204:4bff:fe01:de8a]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 42BE85C43; Sat, 9 Feb 2013 18:52:50 +0100 (CET) Message-ID: <51168CF6.4030204@FreeBSD.org> Date: Sat, 09 Feb 2013 18:52:54 +0100 From: Dimitry Andric Organization: The FreeBSD Project User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:19.0) Gecko/20130117 Thunderbird/19.0 MIME-Version: 1.0 To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-toolchain@FreeBSD.org Subject: Re: bin/175930: clang does not define __STDC_ISO_10646__, despite having Unicode in wchar_t References: <201302091603.r19G3Je7088418@freefall.freebsd.org> In-Reply-To: <201302091603.r19G3Je7088418@freefall.freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Feb 2013 17:53:02 -0000 On 2013-02-09 17:03, linimon@FreeBSD.org wrote:> Old Synopsis: CLang does not define __STDC_ISO_10646__, despite having Unicode in wchar_t > New Synopsis: clang does not define __STDC_ISO_10646__, despite having Unicode in wchar_t > > Responsible-Changed-From-To: freebsd-bugs->freebsd-toolchain > Responsible-Changed-By: linimon > Responsible-Changed-When: Sat Feb 9 16:02:36 UTC 2013 > Responsible-Changed-Why: > let's see if anyone on toolchain@ has an opinion. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=175930 I don't think this has anything to do with clang (or gcc, for that matter). It is a potential issue with our system headers, specifically . Our wchar_t is either int or unsigned int (on armeabi), so I guess it should not be a problem to define a sensible value for the __STDC_ISO_10646__ macro there. As to what the exact value should be, I have no idea really. The C99 standard says only this: __STDC_ISO_10646__ An integer constant of the form yyyymmL (for example, 199712L), intended to indicate that values of type wchar_t are the coded representations of the characters defined by ISO/IEC 10646, along with all amendments and technical corrigenda as of the specified year and month. GNU libc has this: /* wchar_t uses ISO 10646-1 (2nd ed., published 2000-09-15) / Unicode 3.1. */ #define __STDC_ISO_10646__ 200009L So maybe that is a good value for us too?