Date: Sat, 24 Nov 2012 10:45:01 +0000 From: David Chisnall <theraven@theravensnest.org> To: Dimitry Andric <dim@freebsd.org> Cc: toolchain@freebsd.org Subject: Re: [patch][libc++]using some undeclared functions with -std=c++98, -std=c++03 or -ansi Message-ID: <76D35059-88C3-49F3-A871-3402A49875CD@theravensnest.org> In-Reply-To: <50AFEA5D.2020607@FreeBSD.org> References: <50AEB0A1.3090803@kbh.biglobe.ne.jp> <50AFEA5D.2020607@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 23 Nov 2012, at 21:27, Dimitry Andric wrote: > Note there are also other problems when compiling libc++ with = -std=3Dc++98 > and -std=3Dc++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. David=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?76D35059-88C3-49F3-A871-3402A49875CD>