From owner-freebsd-current@FreeBSD.ORG Fri Aug 23 13:54:47 2013 Return-Path: Delivered-To: current@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 2EBF984F; Fri, 23 Aug 2013 13:54:47 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wg0-x22d.google.com (mail-wg0-x22d.google.com [IPv6:2a00:1450:400c:c00::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D650E2903; Fri, 23 Aug 2013 13:54:45 +0000 (UTC) Received: by mail-wg0-f45.google.com with SMTP id n12so580850wgh.24 for ; Fri, 23 Aug 2013 06:54:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=i1h0wGs9L9avCtKf5QdDzQDM1BJsfe8T3YYOSYXWg2Q=; b=BGEh+o9QO8LUW/TPdYG53rOMUuIdTo5zNaiPKF7X+3JFxqbVQ4d1Vhv2iWlR3Kiprv dfxeaHbOpAJ2SvX+ul7Bk3zkl0Hl1J6GYQaa6PTIf1iw2fhf4/xg3+scBF4T3EoAHsMT KT7HRX0fBjhigKem4Y2z8+pGaJVf2orruF3ndPsajP8iGVh8yPkCbNN3W0OyWZXAzkI8 dMhhoiZmENNN60NCnCDyUsRIpAeQqLjhTPJUq2nxfWYsQo15ECfV3abEY2gUFcSuSNm6 qpUitV4vcEKgDdFl2YqdU4RzBdYVPy4x6uCoVjM/eeWtx85ZktX+aVchulYNdtGZ7HDs 0DYw== MIME-Version: 1.0 X-Received: by 10.194.122.129 with SMTP id ls1mr1809538wjb.37.1377266084228; Fri, 23 Aug 2013 06:54:44 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.217.116.136 with HTTP; Fri, 23 Aug 2013 06:54:44 -0700 (PDT) In-Reply-To: <20130823114635.GB64913@zxy.spb.ru> References: <20130822200902.GG94127@funkthat.com> <105E26EE-8471-49D3-AB57-FBE2779CF8D0@FreeBSD.org> <5CE4B5FA-9DA0-45E4-8D67-161E0829FE6B@FreeBSD.org> <52173C8D.20608@freebsd.org> <20130823114635.GB64913@zxy.spb.ru> Date: Fri, 23 Aug 2013 06:54:44 -0700 X-Google-Sender-Auth: TpN1h702denT-HSGus0oeUfMZz0 Message-ID: Subject: Re: patch to add AES intrinsics to gcc From: Adrian Chadd To: Slawa Olhovchenkov Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "re@FreeBSD.org Engineering Team" , "current@freebsd.org" , Bernhard Fr?hlich , John-Mark Gurney , David Chisnall , toolchain@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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Aug 2013 13:54:47 -0000 Hi! If firewire code doesn't build on clang correctly, have you filed a bug so it gets looked at before 10.0 is released? that's pretty broken code/behaviour. -adrian On 23 August 2013 04:46, Slawa Olhovchenkov wrote: > On Fri, Aug 23, 2013 at 06:42:21PM +0800, Julian Elischer wrote: > > > On 8/23/13 6:35 PM, David Chisnall wrote: > > > On 23 Aug 2013, at 10:58, Bernhard Fr?hlich 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=any 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: > > >> > > >> 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 > > >> > > >> the full list: > > >> http://dpaste.com/1354075/ > > >> > > >> A possible hack could be to add a check for USE_GCC=any to behave like > > >> a USE_GCC=yes on HEAD on the affected platforms. This pulls in > lang/gcc > > >> from ports for a lot of people on HEAD I suppose. > > >> > > >> 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). > > no, I believe we have said that 10 would ship with clang by default. > > 10 from this winner have broken firewire code when building by clang > -- cannot resume from sleep. > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >