From owner-freebsd-toolchain@FreeBSD.ORG Fri Aug 23 10:35:49 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 CD8DBCCF; Fri, 23 Aug 2013 10:35:49 +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 983DA2C89; Fri, 23 Aug 2013 10:35:49 +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 r7NAZjLl052159 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 23 Aug 2013 10:35:46 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: Fri, 23 Aug 2013 11:35:40 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <5CE4B5FA-9DA0-45E4-8D67-161E0829FE6B@FreeBSD.org> References: <20130822200902.GG94127@funkthat.com> <105E26EE-8471-49D3-AB57-FBE2779CF8D0@FreeBSD.org> To: =?iso-8859-1?Q?Bernhard_Fr=F6hlich?= X-Mailer: Apple Mail (2.1508) Cc: toolchain@FreeBSD.org, John-Mark Gurney , "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 10:35:49 -0000 On 23 Aug 2013, at 10:58, Bernhard Fr=F6hlich wrote: > I don't know if you are aware that IF you really do that we will have = serious > problems to ship packages for 10. USE_GCC=3Dany is the fallback in the > portstree for all ports that are unable to build with clang which was = introduced > when HEAD switched to clang as default cc. Right now there are 150 = ports in > the tree that use this fallback and quite a few of them are high = profile ports: >=20 > the highlights: > audio/nas devel/mingw32-binutils emulators/qemu = emulators/virtualbox-ose > emulators/wine lang/go lang/v8 mail/courier math/fftw3 = multimedia/libxine > multimedia/gstreamer multimedia/gstreamer-plugins multimedia/x264 > security/clamav >=20 > the full list: > http://dpaste.com/1354075/ >=20 > A possible hack could be to add a check for USE_GCC=3Dany to behave = like > a USE_GCC=3Dyes on HEAD on the affected platforms. This pulls in = lang/gcc > from ports for a lot of people on HEAD I suppose. >=20 > We certainly need to do that switch to remove the ancient gcc from = base > some time but with my portmgr hat on I can only say we don't plan to = do that > before 10.0 especially not if we are only talking about a few weeks = time window. That is unfortunate. We have said for over a year that 10.0 should not = ship with gcc. I can delay committing the patch to flip the switch = until later in the code slush, if re approves, but ports that require = gcc should be building with gcc from ports (which will also improve code = quality, as gcc 4.6/7 produce significantly better code than 4.2.1). David