Date: Sun, 25 Nov 2012 18:31:24 +0100 From: Dimitry Andric <dim@FreeBSD.org> To: David Chisnall <theraven@theravensnest.org> Cc: toolchain@freebsd.org Subject: Re: [patch][libc++]using some undeclared functions with -std=c++98, -std=c++03 or -ansi Message-ID: <50B255EC.9040602@FreeBSD.org> In-Reply-To: <76D35059-88C3-49F3-A871-3402A49875CD@theravensnest.org> References: <50AEB0A1.3090803@kbh.biglobe.ne.jp> <50AFEA5D.2020607@FreeBSD.org> <76D35059-88C3-49F3-A871-3402A49875CD@theravensnest.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2012-11-24 11:45, David Chisnall wrote: > On 23 Nov 2012, at 21:27, Dimitry Andric wrote: >> Note there are also other problems when compiling libc++ with -std=c++98 >> and -std=c++03, such as complaints about namespacing and such. I am not >> entirely sure libc++ is fully supported yet under those restrictions. :) > > In theory, the libc++ headers that are part of the C++03 spec (i.e. not things like <stdatomic>) should work in C++98 / C++03 mode, however the implementation in libc++ must be compiled in C++11 mode. > > To upstream this patch, the __LONG_LONG_SUPPORTED flag should be unconditionally set for non-FreeBSD flags in the __config file in libc++. This will have no functionality change on other platforms. I have posted a proposed patch to the upstream mailing list here: http://lists.cs.uiuc.edu/pipermail/cfe-commits/Week-of-Mon-20121119/068587.html If it is accepted as-is, I will merge it immediately.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?50B255EC.9040602>