From owner-freebsd-toolchain@freebsd.org Sat Mar 19 08:44:00 2016 Return-Path: Delivered-To: freebsd-toolchain@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BFCC7AD4A7E for ; Sat, 19 Mar 2016 08:44:00 +0000 (UTC) (envelope-from dc552@hermes.cam.ac.uk) Received: from ppsw-43.csi.cam.ac.uk (ppsw-43.csi.cam.ac.uk [131.111.8.143]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8D9DEE64; Sat, 19 Mar 2016 08:44:00 +0000 (UTC) (envelope-from dc552@hermes.cam.ac.uk) X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from [195.55.253.10] (port=22885 helo=[10.30.2.16]) by ppsw-43.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.159]:587) with esmtpsa (PLAIN:dc552) (TLSv1:ECDHE-RSA-AES256-SHA:256) id 1ahCUH-0004kA-mn (Exim 4.86_36-e07b163) (return-path ); Sat, 19 Mar 2016 08:43:57 +0000 Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) Subject: Re: c++/libc++ help needed for chromium update From: David Chisnall In-Reply-To: Date: Sat, 19 Mar 2016 08:43:54 +0000 Cc: Christoph Moench-Tegeder , freebsd-toolchain@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <20160316212749.GA1426@squirrel.exwg.net> <458AB9BF-4D4F-4F72-B2D7-79ACC8E19108@FreeBSD.org> <20160317113829.GA1752@squirrel.exwg.net> To: Dimitry Andric X-Mailer: Apple Mail (2.2104) Sender: "Dr D. Chisnall" X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Mar 2016 08:44:00 -0000 On 18 Mar 2016, at 17:22, Dimitry Andric 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