From owner-freebsd-toolchain@FreeBSD.ORG Fri Aug 23 12:56:17 2013 Return-Path: Delivered-To: toolchain@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id B9EC2FB5; Fri, 23 Aug 2013 12:56:17 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from theravensnest.org (theraven.freebsd.your.org [216.14.102.27]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 8457C2529; Fri, 23 Aug 2013 12:56:17 +0000 (UTC) Received: from c120.sec.cl.cam.ac.uk (c120.sec.cl.cam.ac.uk [128.232.18.120]) (authenticated bits=0) by theravensnest.org (8.14.5/8.14.5) with ESMTP id r7NCuEDv054537 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 23 Aug 2013 12:56:15 GMT (envelope-from theraven@FreeBSD.org) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) Subject: Re: patch to add AES intrinsics to gcc From: David Chisnall In-Reply-To: <521754E6.3030906@FreeBSD.org> Date: Fri, 23 Aug 2013 13:56:14 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <422728FC-CE88-4AEF-AD10-3BF8910A2109@FreeBSD.org> References: <20130822200902.GG94127@funkthat.com> <105E26EE-8471-49D3-AB57-FBE2779CF8D0@FreeBSD.org> <5CE4B5FA-9DA0-45E4-8D67-161E0829FE6B@FreeBSD.org> <52173C8D.20608@freebsd.org> <521754E6.3030906@FreeBSD.org> To: Andriy Gapon X-Mailer: Apple Mail (2.1508) Cc: toolchain@FreeBSD.org, "re@FreeBSD.org Engineering Team" , current@FreeBSD.org X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Aug 2013 12:56:17 -0000 On 23 Aug 2013, at 13:26, Andriy Gapon wrote: > 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. Nathan has already dealt with this. > 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. So you don't want a working debugger? Our gdb doesn't work at all on = MIPS and barely works with code compiled with clang or a recent gcc. We = are planning on importing LLDB soon (Ed Maste has been working on it, = funded by the FreeBSD Foundation), and it is a C++11 code base. It will = not build with our gcc or with our libstdc++ (and, in fact, since it = uses the LLVM libraries, will require LLVM in base to link libc++).=20 Or perhaps you don't care about flattened device trees. The device tree = compiler that we have in base is written in C++ and contains numerous = occurrences of ugly code to make it work with old compilers. I will be = very happy to remove a load of hacks once C++11 support is available in = the base system (not for 10.0, as dtc is used on a lot of tier 2 archs = where gcc is still default). David