From owner-freebsd-arch@FreeBSD.ORG Sun Jan 13 19:30:41 2013 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 3AF47819 for ; Sun, 13 Jan 2013 19:30:41 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from mail-ie0-f176.google.com (mail-ie0-f176.google.com [209.85.223.176]) by mx1.freebsd.org (Postfix) with ESMTP id 01AF2789 for ; Sun, 13 Jan 2013 19:30:40 +0000 (UTC) Received: by mail-ie0-f176.google.com with SMTP id 13so4228754iea.21 for ; Sun, 13 Jan 2013 11:30:34 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:sender:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to:x-mailer:x-gm-message-state; bh=3MIDV+mFMyf/Rvl8Jr8Xb8AYW5Mo8QnwrRl0LXuLcdE=; b=BmHqG92gce1DIItlNvT84j+X8ITrGnp+NnSRe7/7xof395GVxHqR/YYWZ4Pp8y2YK5 zOCX6sxqOtxxKJQdfYDrxhTawzfzJeexTw3Aa7zEIm5E2SXqaT+mpSJkqvR1yuvCn6ZQ qmI+mBJgLgG5WafKWVscwuvdiZjf9f7nWZknTVVJy7vP46xiMf03/NVCK1eOoQ/H8mxG IISw0muBBMFRhU/qoUGZUI0Rf9Zs5fGtLoMO3nfJj1hNPOqrYF3ySNr6d7PcH6Yrh3+I szZrBpPf5Usfz8gMkXJ1pH3RbxSvLNIfiXmKsHMnW/yu6S5wr9Png5uJ5GiY9Z3qRHvF 0BYQ== X-Received: by 10.42.101.144 with SMTP id e16mr62575558ico.5.1358105433962; Sun, 13 Jan 2013 11:30:33 -0800 (PST) Received: from 53.imp.bsdimp.com (50-78-194-198-static.hfc.comcastbusiness.net. [50.78.194.198]) by mx.google.com with ESMTPS id iw5sm4693638igc.5.2013.01.13.11.30.31 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 13 Jan 2013 11:30:32 -0800 (PST) Sender: Warner Losh Subject: Re: how long to keep support for gcc on x86? Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=us-ascii From: Warner Losh In-Reply-To: Date: Sun, 13 Jan 2013 12:30:30 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20130112233147.GK1410@funkthat.com> <20130113014242.GA61609@troutmask.apl.washington.edu> To: Adrian Chadd X-Mailer: Apple Mail (2.1085) X-Gm-Message-State: ALoCoQmVs+ynhQBYMO+k3AX+iwrYvHqBaTzHgQixQDjHHK9hToeLuIOQSljv2Iar8RCVRUGg36Q3 Cc: Steve Kargl , freebsd-arch@freebsd.org 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 19:30:41 -0000 On Jan 12, 2013, at 8:30 PM, Adrian Chadd wrote: > IMHO gcc shuld be available until all of the platforms that we > currently ship FreeBSD on gets clang support. >=20 > This includes MIPS (which is there, but I don't think the default MIPS > build uses clang at the moment) and ia64, which Marcel has been > dutifully working on. >=20 > Please also note that people can and will compile FreeBSD on a > non-default-system compiler ; so deprecating gcc (either support or > framework) should be considered carefully. When this was talked about at the clang summit, the overwhelming opinion = expressed was "better with clang". If you can make things better with = clang, great. However, gcc still must work. So no. You can't break gcc build of the kernel. You can make it better = with clang, but you must still support gcc, especially for something = like this. Warner >=20 > Adrian >=20 >=20 > On 12 January 2013 17:42, Steve Kargl = wrote: >> 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? >>=20 >> IMHO, gcc should be available until after 10.0 is branched. >>=20 >>> I'm asking because clang support AES-NI, but gcc does not... >>=20 >> 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. >>=20 >> -- >> Steve >> _______________________________________________ >> freebsd-arch@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-arch >> To unsubscribe, send any mail to = "freebsd-arch-unsubscribe@freebsd.org" > _______________________________________________ > freebsd-arch@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arch > To unsubscribe, send any mail to = "freebsd-arch-unsubscribe@freebsd.org"