From owner-freebsd-toolchain@FreeBSD.ORG Fri Aug 23 12:12:37 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 C2579D28; Fri, 23 Aug 2013 12:12:37 +0000 (UTC) (envelope-from c.kworr@gmail.com) Received: from mail-la0-x22c.google.com (mail-la0-x22c.google.com [IPv6:2a00:1450:4010:c03::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id AB28B2290; Fri, 23 Aug 2013 12:12:36 +0000 (UTC) Received: by mail-la0-f44.google.com with SMTP id eo20so419871lab.3 for ; Fri, 23 Aug 2013 05:12:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:newsgroups:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=GrME/9gpdIKS9OLal7SsZMmGtskhONsAHgUvi4rSY4U=; b=c5+wzu0RzitbEzQE2x75FJJOqYZvULeWhIupsOQAtOAmPaD49Grds4CS37YeFLwiau FFNj5J5mQh+WcjDqtR1CtPeE0Au6nO4A4xdd6FmjsqjSYPBBr4QdGK5dULzDb4Tjzu+f ZxQ4TJbu2mouAFnpD4e46JzegoROsxiPWdA9HzKz3yFidbxDgt9Q2n1m6mvXERzeXBGk 2KukSCJaBu1ZcoVGY0Ynmjs07rAs+vZE1LW9nT1o+XT0OQ4aXXs8IC6D/vHRoTxsNV/Q xhkFSI3b4cDrhumYjKkCp1QDx/9RJTapFKHn5lCZB12OxOxnHdqSU/WzNxKdacmJbs1p PRVw== X-Received: by 10.112.26.106 with SMTP id k10mr15655061lbg.27.1377259954401; Fri, 23 Aug 2013 05:12:34 -0700 (PDT) Received: from [192.168.1.128] (mau.donbass.com. [92.242.127.250]) by mx.google.com with ESMTPSA id b6sm6596332lae.0.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 23 Aug 2013 05:12:33 -0700 (PDT) Message-ID: <521751AF.6040905@gmail.com> Date: Fri, 23 Aug 2013 15:12:31 +0300 From: Volodymyr Kostyrko User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130809 Thunderbird/17.0.8 MIME-Version: 1.0 Newsgroups: gmane.os.freebsd.current To: =?UTF-8?B?QmVybmhhcmQgRnLDtmhsaWNo?= Subject: Re: patch to add AES intrinsics to gcc References: <20130822200902.GG94127@funkthat.com> <105E26EE-8471-49D3-AB57-FBE2779CF8D0@FreeBSD.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Cc: toolchain@freebsd.org, 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: Fri, 23 Aug 2013 12:12:37 -0000 23.08.2013 12: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. I object. Many ports that compiles perfectly on gcc 4.2.1 can't be compiled with lang/gcc. I checked this once and the number of ports that require strictly gcc 4.2.1 was bigger for me then number of ports that can't be compiled with clang but fill fine on lang/gcc. I'll gonna recheck whether lang/gcc42 is sufficient for them. But I have that bad feeling... -- Sphinx of black quartz, judge my vow.