From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id B82E51387D3 for ; Sat, 25 Oct 2014 13:42:28 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 44356E083E; Sat, 25 Oct 2014 13:42:21 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 502DFE0882 for ; Sat, 25 Oct 2014 13:42:20 +0000 (UTC) Received: from [192.168.42.191] (unknown [91.252.195.148]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: lu_zero) by smtp.gentoo.org (Postfix) with ESMTPSA id 10352340323 for ; Sat, 25 Oct 2014 13:42:17 +0000 (UTC) Message-ID: <544BA8B5.2090405@gentoo.org> Date: Sat, 25 Oct 2014 15:42:13 +0200 From: Luca Barbato User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:33.0) Gecko/20100101 Thunderbird/33.0 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] status of bugs blocking gcc-4.8.3 References: <544A888D.5020702@gentoo.org> <544B7FB9.7010504@gentoo.org> <87y4s4csnx.fsf@jackdaw.kyomu.43-1.org> In-Reply-To: <87y4s4csnx.fsf@jackdaw.kyomu.43-1.org> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Archives-Salt: c4ecd1ba-9480-4f64-933a-e1f57c7f947e X-Archives-Hash: 381e3031f56cbda5a2ceb17ce2dd279e On 25/10/14 13:09, Matthias Maier wrote: > >> Not sure if the llvm C++ runtime might help here or it is any better >> than the one provided by gnu, but might be a good time to gather >> volunteers to provide a mean to use clang as main compiler out of box. > > libc++ makes stricter ABI guarantees [1]. But from personal experience I > would not consider it a replacement for libstdc++ in the near future. Probably we could join forces with FreeBSD to help pushing fixes to applications upstream. > I have set up some lxc containers with clang/libc++ with promising > results (and I plan to keep up testing with it once in a while). Could you please blog or add some notes to the wiki about it? lu