Date: Tue, 12 Jul 2016 06:57:58 +0300 From: Andrey Chernov <ache@freebsd.org> To: Mark Millard <markmi@dsl-only.net>, svn-src-head@freebsd.org, FreeBSD Current <freebsd-current@freebsd.org>, freebsd-stable@freebsd.org Cc: Bruce Evans <brde@optusnet.com.au> Subject: Re: svn commit: r302601 - in head/sys: arm/include arm64/include [__WCHAR_MAX definition mostly] Message-ID: <b4d1b3d9-9577-3f89-c13e-8c46d1ddee95@freebsd.org> In-Reply-To: <46153340-D2F4-48BD-B738-4792BC25FA3F@dsl-only.net> References: <46153340-D2F4-48BD-B738-4792BC25FA3F@dsl-only.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12.07.2016 5:44, Mark Millard wrote: > My understanding of the criteria for __WCHAR_MIN and __WCHAR_MAX: > > A) __WCHAR_MIN and __WCHAR_MAX: same type as the integer promotion of > ___wchar_t (if that is distinct). > B) __WCHAR_MIN is the low value for ___wchar_t as an integer type; not > necessarily a valid char value > C) __WCHAR_MAX is the high value for ___wchar_t as an integer type; not > necessarily a valid char value It seems you are right about "not a valid char value", I'll back this change out. > As far as I know arm FreeBSD uses unsigned character types (of whatever > width). Probably it should be unsigned for other architectures too, clang does not generate negative values with L'<char>' literals and locale use only positive values too.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b4d1b3d9-9577-3f89-c13e-8c46d1ddee95>