From owner-freebsd-toolchain@FreeBSD.ORG  Tue Sep 18 08:32:11 2012
Return-Path: <owner-freebsd-toolchain@FreeBSD.ORG>
Delivered-To: toolchain@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id 16841106566C;
	Tue, 18 Sep 2012 08:32:11 +0000 (UTC)
	(envelope-from theraven@FreeBSD.org)
Received: from theravensnest.org (theraven.freebsd.your.org [216.14.102.27])
	by mx1.freebsd.org (Postfix) with ESMTP id D51B48FC14;
	Tue, 18 Sep 2012 08:32:10 +0000 (UTC)
Received: from [192.168.0.2] (cpc2-cmbg15-2-0-cust445.5-4.cable.virginmedia.com
	[86.26.13.190]) (authenticated bits=0)
	by theravensnest.org (8.14.5/8.14.5) with ESMTP id q8I8W2PU077207
	(version=TLSv1/SSLv3 cipher=DHE-DSS-AES128-SHA bits=128 verify=NO);
	Tue, 18 Sep 2012 08:32:03 GMT (envelope-from theraven@FreeBSD.org)
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=us-ascii
From: David Chisnall <theraven@FreeBSD.org>
In-Reply-To: <20120917191028.GA42648@lor.one-eyed-alien.net>
Date: Tue, 18 Sep 2012 09:31:57 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <1B405D52-65B8-44A2-B350-0973A8B254CB@FreeBSD.org>
References: <20120917191028.GA42648@lor.one-eyed-alien.net>
To: Brooks Davis <brooks@FreeBSD.org>
X-Mailer: Apple Mail (2.1278)
Cc: toolchain@FreeBSD.org
Subject: Re: enabling libc++ by default when building with clang
X-BeenThere: freebsd-toolchain@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Maintenance of FreeBSD's integrated toolchain
	<freebsd-toolchain.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-toolchain>, 
	<mailto:freebsd-toolchain-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-toolchain>
List-Post: <mailto:freebsd-toolchain@freebsd.org>
List-Help: <mailto:freebsd-toolchain-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-toolchain>, 
	<mailto:freebsd-toolchain-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Sep 2012 08:32:11 -0000

On 17 Sep 2012, at 20:10, Brooks Davis wrote:

> One key question is, when do we want to throw this switch?  Do we do =
it
> now so people using clang start using it sooner or do we wait until
> we've switched the default compiler and things have settled a bit?

As dim says, enabling it does not mean requiring things to use it.  I =
would like to flip this switch as soon as possible so that it's easy for =
ports people maintaining C++ ports to see if their stuff breaks with =
-stdlib=3Dlibc++.  A few have already tested this, but I'd like to see =
much wider testing. =20

The more important switches to worry about are:

- Changing the default for -stdlib=3D to libc++ (it's currently =
libstdc++.  I think I'll probably make it libc++ when std=3D{c,gnu}++11 =
soon)
- Removing libstdc++ from base and putting it in the compat9 port.

These have the potential to impact users significantly.  Simply having =
libc++.{so,a} on their system does not unless they explicitly choose to =
test it.

David=