From owner-freebsd-current@FreeBSD.ORG  Fri Aug 23 18:17:42 2013
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTP id 797493B0;
 Fri, 23 Aug 2013 18:17:42 +0000 (UTC)
 (envelope-from julian@freebsd.org)
Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 468B52910;
 Fri, 23 Aug 2013 18:17:42 +0000 (UTC)
Received: from Julian-MBP3.local (etroy.elischer.org [121.45.226.51])
 (authenticated bits=0)
 by vps1.elischer.org (8.14.6/8.14.6) with ESMTP id r7NIHabb001677
 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO);
 Fri, 23 Aug 2013 11:17:39 -0700 (PDT)
 (envelope-from julian@freebsd.org)
Message-ID: <5217A73A.7090402@freebsd.org>
Date: Sat, 24 Aug 2013 02:17:30 +0800
From: Julian Elischer <julian@freebsd.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8;
 rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Andriy Gapon <avg@FreeBSD.org>
Subject: Re: patch to add AES intrinsics to gcc
References: <20130822200902.GG94127@funkthat.com>
 <105E26EE-8471-49D3-AB57-FBE2779CF8D0@FreeBSD.org>
 <CAE-m3X324rbdP_C=az4eO-EkMcR-yFAeRG7S4q+MUsnMezGddw@mail.gmail.com>
 <5CE4B5FA-9DA0-45E4-8D67-161E0829FE6B@FreeBSD.org>
 <52173C8D.20608@freebsd.org>
 <D879DDDA-EF9D-470A-A82E-04E83DB2A7E4__13641.8188493282$1377255996$gmane$org@FreeBSD.org>
 <521754E6.3030906@FreeBSD.org>
In-Reply-To: <521754E6.3030906@FreeBSD.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: toolchain@FreeBSD.org, David Chisnall <theraven@FreeBSD.org>,
 current@FreeBSD.org, "re@FreeBSD.org Engineering Team" <re@FreeBSD.org>
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Aug 2013 18:17:42 -0000

On 8/23/13 8:26 PM, Andriy Gapon wrote:
> on 23/08/2013 14:06 David Chisnall said the following:
>> Our gcc is from 2007.  It has no C11, no C++11 support.  It has bugs in its
>> atomic generation so you can't use it sensibly without lots of inline
>> assembly (which it doesn't support for newer architectures) for
>> multithreaded things.
>>
>> Our libstdc++ is ancient and doesn't work with modern C++ codebases.
> On the other hand these tools are perfect for building FreeBSD kernel and base.
> Extrapolating my experience with base GCC I am very confident in it as a
> FreeBSD development tool.
> Extrapolating my experience with Clang I am not yet confident in it as a
> FreeBSD development tool.
>
> I do not care about C11, C++11 and modern C++ codebases.  I care about what's
> in /usr/src and what gets compiled by buildkernel/buildworld.  That's just me,
> of course.  But, OTOH, those who care modern C++ codebases should be perfectly
> capable to install a compiler from ports or switch to clang as their default
> compiler.
>
+1

I'd like to see it still be "there if you need it" in 10

in 11 it's in ports