From owner-freebsd-toolchain@FreeBSD.ORG Sat Aug 24 09:46:37 2013 Return-Path: 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 3E867FAB; Sat, 24 Aug 2013 09:46:37 +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 0A71924CC; Sat, 24 Aug 2013 09:46:36 +0000 (UTC) Received: from [192.168.0.2] (cpc27-cmbg15-2-0-cust235.5-4.cable.virginmedia.com [86.27.188.236]) (authenticated bits=0) by theravensnest.org (8.14.5/8.14.5) with ESMTP id r7O9kXPe008896 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sat, 24 Aug 2013 09:46:34 GMT (envelope-from theraven@FreeBSD.org) Content-Type: text/plain; charset=iso-8859-1 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: Date: Sat, 24 Aug 2013 10:46:29 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <7D444AD2-D5DD-4F3A-BF43-720D68009657@FreeBSD.org> References: <20130822200902.GG94127@funkthat.com> <105E26EE-8471-49D3-AB57-FBE2779CF8D0@FreeBSD.org> <521751AF.6040905@gmail.com> To: =?iso-8859-1?Q?Bernhard_Fr=F6hlich?= X-Mailer: Apple Mail (2.1508) Cc: toolchain@FreeBSD.org, Volodymyr Kostyrko , John-Mark Gurney , 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: Sat, 24 Aug 2013 09:46:37 -0000 On 23 Aug 2013, at 13:30, Bernhard Fr=F6hlich wrote: > lang/gcc42 is on the list of ports that have USE_GCC=3Dany. So you = would need > to fix it first to be able to compile it with clang 3.3 from base. What is the issue with the gcc 4.2.1 build (aside from the fact that it = has a terrifying number of warnings when built with any recent = compiler)? The gcc 4.2.1 in base builds with clang - that's how we = currently build it in head... David