From owner-freebsd-ports@FreeBSD.ORG Thu Dec 18 19:13:37 2014 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 83D7599D; Thu, 18 Dec 2014 19:13:37 +0000 (UTC) Received: from mail-pd0-x233.google.com (mail-pd0-x233.google.com [IPv6:2607:f8b0:400e:c02::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49973105D; Thu, 18 Dec 2014 19:13:37 +0000 (UTC) Received: by mail-pd0-f179.google.com with SMTP id fp1so1975947pdb.24; Thu, 18 Dec 2014 11:13:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=+xmpZdoMcVfKiQSBuMyzFvGknYzx3AXeytKJBe+ZynU=; b=VRCjSciVRkM/LMPYUbgHG0GCBK4oXdjQUjZvwu8NgPNey+MGNZRfkh+43sjMRGAd18 g61qIou4fBG0c4cjapECaMRzqt2+pBNm/2F3YAbaZOMLsq2K+p9K7wKR8PozWLvQNEBl m187IAC+83Ujh22pv1VXVhJ2bnmX798Dg3IzpREmXKFjdoC6Q7zX+Noh/JyJ8XZyxyWH ZYqHkg5qQnCT/PssSzgIccqX5oVK4q9Fwlhse1zNj4Vjo+Na9MxLMaAuGJbeOqAYilzk OiZ7NHzLY4dNZl/XTe3Defgi85C2Ee5NdtfGoJYUUbxeScGpAyDZTOxnB01lOyfUHvpf DDug== X-Received: by 10.70.137.1 with SMTP id qe1mr6127549pdb.90.1418930016794; Thu, 18 Dec 2014 11:13:36 -0800 (PST) Received: from ?IPv6:2601:8:ab80:7d6:4965:32c9:fd93:5519? ([2601:8:ab80:7d6:4965:32c9:fd93:5519]) by mx.google.com with ESMTPSA id eo4sm7401811pbb.87.2014.12.18.11.13.35 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 18 Dec 2014 11:13:35 -0800 (PST) Content-Type: multipart/signed; boundary="Apple-Mail=_7E7A7273-DB8E-4D03-BA0E-96DA9BB5A08E"; protocol="application/pgp-signature"; micalg=pgp-sha512 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: RFT: Please help testing the llvm/clang 3.5.0 import From: Garrett Cooper In-Reply-To: Date: Thu, 18 Dec 2014 11:13:36 -0800 Message-Id: <6C1932BE-8B1D-44E1-AAFA-C24756434BDC@gmail.com> References: <8598B1D4-5485-426F-B6D6-22BF26AC5FE1@FreeBSD.org> To: Dimitry Andric X-Mailer: Apple Mail (2.1878.6) Cc: FreeBSD ARM , FreeBSD-Current , FreeBSD ports X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Dec 2014 19:13:37 -0000 --Apple-Mail=_7E7A7273-DB8E-4D03-BA0E-96DA9BB5A08E Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 On Dec 18, 2014, at 5:02, Dimitry Andric wrote: > On 18 Dec 2014, at 02:17, NGie Cooper wrote: >>=20 >> On Fri, Nov 28, 2014 at 1:03 PM, Dimitry Andric = wrote: > ... >> As a request to speed up the build process further, >> - Would it be [easily] possible in the clang35 branch to bootstrap >> the compiler for a specific architecture? The bootstrap / cross >> compiler for instance always builds N targets instead of building = just >> the desired TARGET/TARGET_ARCH combo. >=20 > It's not very easy, at least not without breaking various parts of our > fragile build system, but I surely want to put something like this on > the TODO list for *after* the import has completed. >=20 > The branch is making progress right now, and I would not want to > complicate matters further by introducing yet another tricky feature. = :) Fair enough :). >> - Could a "MK_CLANG_ALL_TARGETS" or something similar option be >> added to src.opts.mk to fine tune this process for those of us who >> don't want to build a cross-compile toolchain every iteration for our >> target MACHINE/MACHINE_ARCH? >=20 > I would be fine with something like this, as long as it is turned off = by > default, or if it is only used for the bootstrap stages. It is = actually > an extremely useful feature of clang that you can target multiple > architectures with one compiler binary. Yes. If make tinderbox could use this it would be useful, otherwise, for = most folks it seems like a less interesting feature. > A more interesting case would be to remodel the build system so it can > use one toolchain (external, or pkg-ng'd, maybe?) for building an = entire > universe. With clang, that should be relatively easy to do. Agreed. bdrewery is working on something similar to that internally for = Isilon. Building the same toolchain N times internally when building the = system and your upstream revision of FreeBSD doesn=92t change is like = testing your sanity =97 not much changes with the bootstrap = compiler/toolchain then! Thanks for the reply :)! --Apple-Mail=_7E7A7273-DB8E-4D03-BA0E-96DA9BB5A08E Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQEcBAEBCgAGBQJUkydgAAoJEMZr5QU6S73eA5MH/Rocvs4q+qhcrhIzhRFcqHGb iuQ0c9VqwmR7BU4aWAMY1qIzBqsEfyImZfUGc/zUAJ+zWQlf8QnJy50Bi5V9kTUO VLin6d7r62VvQu/yUQ0e948w/tlaIRC9kqiEliYZfFqdJMZLfF7ADS69ahzGuSm2 tUQiMLsPE/SMcehspLW/SweT3+fL44UXrzIzxJIAqeP3ea7GPEMQ0+auvqR40yLl iTsTlu2nyCESdWiuQ5tCJoSXjcWRiRsH3fMpCebSwT7oxi0Xn+TDE8PsXSti8doz btDp1abP0F/cQN84fy0xLX+TaUs5XonZe7YgIp080AqbgvhJAZSPy+g1WUsnAvc= =GVVZ -----END PGP SIGNATURE----- --Apple-Mail=_7E7A7273-DB8E-4D03-BA0E-96DA9BB5A08E--