Date: Sat, 19 Mar 2016 08:43:54 +0000 From: David Chisnall <David.Chisnall@cl.cam.ac.uk> To: Dimitry Andric <dim@FreeBSD.org> Cc: Christoph Moench-Tegeder <cmt@burggraben.net>, freebsd-toolchain@freebsd.org Subject: Re: c++/libc++ help needed for chromium update Message-ID: <C525813A-46F7-4BB0-866E-CDD6BF4B25A3@cl.cam.ac.uk> In-Reply-To: <C999DFAB-01E7-41E7-AEFD-43FBF8D41582@FreeBSD.org> References: <20160316212749.GA1426@squirrel.exwg.net> <458AB9BF-4D4F-4F72-B2D7-79ACC8E19108@FreeBSD.org> <20160317113829.GA1752@squirrel.exwg.net> <C999DFAB-01E7-41E7-AEFD-43FBF8D41582@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 18 Mar 2016, at 17:22, Dimitry Andric <dim@FreeBSD.org> wrote: >=20 > We > could enable this feature, but then we'd have to bump our libc++ > version, together with all the followup hassle. There are quite a few ABI-breaking changes in libc++. Some improve = standards compliance and a few improve performance. I=E2=80=99d like = for us to enable them all (with associated so version bump) in 11. At = this point, it might make sense to do the same for libc++ in ports and = move ports over to depending on the ports version on <11. David
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?C525813A-46F7-4BB0-866E-CDD6BF4B25A3>