From owner-freebsd-current@FreeBSD.ORG Tue Aug 27 20:42:33 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 D6ACC28E; Tue, 27 Aug 2013 20:42:33 +0000 (UTC) (envelope-from gerald@pfeifer.com) Received: from ainaz.pair.com (ainaz.pair.com [209.68.2.66]) by mx1.freebsd.org (Postfix) with ESMTP id AD8DB2114; Tue, 27 Aug 2013 20:42:33 +0000 (UTC) Received: from trevally.dhcp.nue.suse.com (nat.nue.novell.com [195.135.221.2]) by ainaz.pair.com (Postfix) with ESMTPSA id EDFEF3F419; Tue, 27 Aug 2013 16:42:23 -0400 (EDT) Date: Tue, 27 Aug 2013 22:42:22 +0200 (CEST) From: Gerald Pfeifer To: Claude Buisson Subject: Re: patch to add AES intrinsics to gcc In-Reply-To: <521B54CF.3020905@orange.fr> Message-ID: References: <20130822200902.GG94127@funkthat.com> <105E26EE-8471-49D3-AB57-FBE2779CF8D0@FreeBSD.org> <5CE4B5FA-9DA0-45E4-8D67-161E0829FE6B@FreeBSD.org> <5217DBAB.5030607@freebsd.org> <86032E72-A569-4946-B4F8-26F687067B31@bsdimp.com> <1380949A-254A-4222-BEDE-0C23E16E4F67@freebsd.org> <8C31A000-6806-4291-98A4-E8291E637BD2@bsdimp.com> <521B54CF.3020905@orange.fr> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Mailman-Approved-At: Tue, 27 Aug 2013 21:49:26 +0000 Cc: re@freebsd.org, current@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: Tue, 27 Aug 2013 20:42:33 -0000 On Mon, 26 Aug 2013, Claude Buisson wrote: > Perhaps you could have a look at the fact that lang/gcc is at 4.6.3, > and lang/gcc46 is no more a snapshot but a true release 4.6.4. I am aware of that. Owed to a strongly voiced desire by users, I am triggering a rebuild of lang/gcc as rarely as possible. So, instead of going from 4.6.4 and soon 4.7.x, I submitted an update to 4.7.3 to portmgr for an -exp run last weekend. > IMHO, lang/gcc must be discontinued, or updated to 4.6.4 and > lang/gcc46 discontinued ? Neither. :-) Of all lang/gcc* ports, lang/gcc is the one to use (and hence keep). And lang/gcc46, lang/gcc47,... will remain in place for a while for use by those interested in an older version (or broken ports requiring one) or those interested in tracker newer versions. Gerald