From owner-freebsd-current@FreeBSD.ORG Sat Aug 24 09:52:27 2013 Return-Path: Delivered-To: freebsd-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 7A881197; Sat, 24 Aug 2013 09:52:27 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from theravensnest.org (theraven.freebsd.your.org [216.14.102.27]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 4875E250A; Sat, 24 Aug 2013 09:52:26 +0000 (UTC) Received: from [192.168.0.2] (cpc27-cmbg15-2-0-cust235.5-4.cable.virginmedia.com [86.27.188.236]) (authenticated bits=0) by theravensnest.org (8.14.5/8.14.5) with ESMTP id r7O9qOPM008921 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sat, 24 Aug 2013 09:52:25 GMT (envelope-from theraven@FreeBSD.org) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) Subject: Re: GCC withdraw From: David Chisnall In-Reply-To: <52180DD0.3080308@freebsd.org> Date: Sat, 24 Aug 2013 10:52:20 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20130822200902.GG94127@funkthat.com> <105E26EE-8471-49D3-AB57-FBE2779CF8D0@FreeBSD.org> <5217413A.9080105@passap.ru> <20130823111647.GT2951@home.opsec.eu> <52174D51.2050601@digsys.bg> <21414.1377258940@critter.freebsd.dk> <5217A7D8.1030806@freebsd.org> <1377285836.31114.13416825.5F534A08@webmail.messagingengine.com> <52180DD0.3080308@freebsd.org> To: Julian Elischer X-Mailer: Apple Mail (2.1508) Cc: freebsd-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: Sat, 24 Aug 2013 09:52:27 -0000 On 24 Aug 2013, at 02:35, Julian Elischer wrote: > I don't know.. whatever RootBSD run, but the fact that I needed gcc = for anything suggests that we should keep it around for a while. Please point to the FreeBSD PRs and clang bug reports that you have = filed about this. I have been running a FreeBSD VM on Xen with the = clang is cc option for over a year and not encountered this problem. David