From owner-freebsd-toolchain@FreeBSD.ORG Sat Sep 6 11:34:47 2014 Return-Path: Delivered-To: freebsd-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 ESMTPS id 1D9CE3C9 for ; Sat, 6 Sep 2014 11:34:47 +0000 (UTC) Received: from theravensnest.org (theraven.freebsd.your.org [216.14.102.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "cloud.theravensnest.org", Issuer "StartCom Class 1 Primary Intermediate Server CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id CED961B13 for ; Sat, 6 Sep 2014 11:34:46 +0000 (UTC) Received: from [192.168.0.7] (cpc14-cmbg15-2-0-cust307.5-4.cable.virginm.net [82.26.1.52]) (authenticated bits=0) by theravensnest.org (8.14.9/8.14.9) with ESMTP id s86BSJko085057 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sat, 6 Sep 2014 11:28:31 GMT (envelope-from theraven@FreeBSD.org) X-Authentication-Warning: theravensnest.org: Host cpc14-cmbg15-2-0-cust307.5-4.cable.virginm.net [82.26.1.52] claimed to be [192.168.0.7] Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: Building clang in buildworld as part of the bootstrap process -- is it really necessary? From: David Chisnall In-Reply-To: <215CB3BB-BA4B-41D9-9CBF-FC0FDEE9492C@gmail.com> Date: Sat, 6 Sep 2014 12:28:14 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <4AF47B56-109E-46A3-8EC4-75B95E063FCF@FreeBSD.org> References: <01C283B7-C9AF-4AE8-A192-FBC7C04D207E@bsdimp.com> <215CB3BB-BA4B-41D9-9CBF-FC0FDEE9492C@gmail.com> To: Garrett Cooper X-Mailer: Apple Mail (2.1878.6) Cc: "freebsd-toolchain@freebsd.org" , "conrad.meyer@emc.com" X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Sep 2014 11:34:47 -0000 On 6 Sep 2014, at 06:47, Garrett Cooper wrote: > Makes sense. I'll do some poking around and see if things could = potentially be optimized with the clang build. On beefy machines it's = not a big deal, but as we know on machines without a ton of memory or = SSDs, it can become painful, as expected. The build system for clang-in-base has improved a bit so, as you say, it = is now reasonably fast on beefy machines (release clang build with the = upstream build system takes 2-3 minutes on a fast machine, about 10 on = my laptop, the one in buildworld isn't quite as good at extracting = parallelism). On slow machines, it can be quite painful. The correct solution to this problem is likely to be to start creating = bootstrap-toolchain packages. This is also likely to be necessary for = architectures like MIPS and PowerPC before 11 anyway, because the host = compiler doesn't have the C++11 support required for bootstrapping a = newer LLVM and clang. We can work around that quite easily if we have = package for the bootstrap toolchain (possibly cross-compiled from an x86 = machine). David