From owner-freebsd-arch@FreeBSD.ORG Sun Jan 13 01:42:48 2013 Return-Path: Delivered-To: freebsd-arch@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id D4B83BF5 for ; Sun, 13 Jan 2013 01:42:48 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) by mx1.freebsd.org (Postfix) with ESMTP id 8EA77170 for ; Sun, 13 Jan 2013 01:42:48 +0000 (UTC) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.5/8.14.5) with ESMTP id r0D1ggPY061704 for ; Sat, 12 Jan 2013 17:42:42 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.5/8.14.5/Submit) id r0D1ggUt061703 for freebsd-arch@FreeBSD.org; Sat, 12 Jan 2013 17:42:42 -0800 (PST) (envelope-from sgk) Date: Sat, 12 Jan 2013 17:42:42 -0800 From: Steve Kargl To: freebsd-arch@FreeBSD.org Subject: Re: how long to keep support for gcc on x86? Message-ID: <20130113014242.GA61609@troutmask.apl.washington.edu> References: <20130112233147.GK1410@funkthat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130112233147.GK1410@funkthat.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jan 2013 01:42:48 -0000 On Sat, Jan 12, 2013 at 03:31:47PM -0800, John-Mark Gurney wrote: > So, now that -current x86 is defaulting to clang, how much longer do we > need to support gcc on platforms that default to clang? IMHO, gcc should be available until after 10.0 is branched. > I'm asking because clang support AES-NI, but gcc does not... The last and only time I had for testing clang's handling of floating point revealed that clang had a few bugs and performance issues. -- Steve