Date: Thu, 18 Dec 2014 11:13:36 -0800 From: Garrett Cooper <yaneurabeya@gmail.com> To: Dimitry Andric <dim@FreeBSD.org> Cc: FreeBSD ARM <freebsd-arm@freebsd.org>, FreeBSD-Current <freebsd-current@freebsd.org>, FreeBSD ports <freebsd-ports@freebsd.org> Subject: Re: RFT: Please help testing the llvm/clang 3.5.0 import Message-ID: <6C1932BE-8B1D-44E1-AAFA-C24756434BDC@gmail.com> In-Reply-To: <D9C5A8D1-2158-4B37-9C9C-067A4DDE6E44@FreeBSD.org> References: <8598B1D4-5485-426F-B6D6-22BF26AC5FE1@FreeBSD.org> <CAGHfRMBPkQiTgW0Eahkoe1QwArBst-BZ-Lawor_CDda1x8K9xg@mail.gmail.com> <D9C5A8D1-2158-4B37-9C9C-067A4DDE6E44@FreeBSD.org>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On Dec 18, 2014, at 5:02, Dimitry Andric <dim@FreeBSD.org> wrote: > On 18 Dec 2014, at 02:17, NGie Cooper <yaneurabeya@gmail.com> wrote: >> >> On Fri, Nov 28, 2014 at 1:03 PM, Dimitry Andric <dim@freebsd.org> 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. > > 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. > > 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? > > 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’t change is like testing your sanity — not much changes with the bootstrap compiler/toolchain then! Thanks for the reply :)! [-- Attachment #2 --] -----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-----help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6C1932BE-8B1D-44E1-AAFA-C24756434BDC>