From owner-freebsd-toolchain@FreeBSD.ORG  Fri Aug 23 12:26:53 2013
Return-Path: <owner-freebsd-toolchain@FreeBSD.ORG>
Delivered-To: toolchain@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 75FE614B;
 Fri, 23 Aug 2013 12:26:53 +0000 (UTC) (envelope-from avg@FreeBSD.org)
Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140])
 by mx1.freebsd.org (Postfix) with ESMTP id 00C212370;
 Fri, 23 Aug 2013 12:26:51 +0000 (UTC)
Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua
 [212.40.38.100])
 by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id PAA28175;
 Fri, 23 Aug 2013 15:26:50 +0300 (EEST)
 (envelope-from avg@FreeBSD.org)
Received: from localhost ([127.0.0.1])
 by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD))
 id 1VCqS1-000PXV-Vv; Fri, 23 Aug 2013 15:26:50 +0300
Message-ID: <521754E6.3030906@FreeBSD.org>
Date: Fri, 23 Aug 2013 15:26:14 +0300
From: Andriy Gapon <avg@FreeBSD.org>
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
 rv:17.0) Gecko/20130810 Thunderbird/17.0.8
MIME-Version: 1.0
To: David Chisnall <theraven@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>
In-Reply-To: <D879DDDA-EF9D-470A-A82E-04E83DB2A7E4__13641.8188493282$1377255996$gmane$org@FreeBSD.org>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: toolchain@FreeBSD.org, Julian Elischer <julian@FreeBSD.org>,
 current@FreeBSD.org, "re@FreeBSD.org Engineering Team" <re@FreeBSD.org>
X-BeenThere: freebsd-toolchain@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Maintenance of FreeBSD's integrated toolchain
 <freebsd-toolchain.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/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: Fri, 23 Aug 2013 12:26:53 -0000

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.

-- 
Andriy Gapon