Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 18 Dec 2014 14:02:58 +0100
From:      Dimitry Andric <dim@FreeBSD.org>
To:        NGie Cooper <yaneurabeya@gmail.com>
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:  <D9C5A8D1-2158-4B37-9C9C-067A4DDE6E44@FreeBSD.org>
In-Reply-To: <CAGHfRMBPkQiTgW0Eahkoe1QwArBst-BZ-Lawor_CDda1x8K9xg@mail.gmail.com>
References:  <8598B1D4-5485-426F-B6D6-22BF26AC5FE1@FreeBSD.org> <CAGHfRMBPkQiTgW0Eahkoe1QwArBst-BZ-Lawor_CDda1x8K9xg@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help

--Apple-Mail=_C5A7933F-460F-431A-BE05-C752275FCCFF
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii

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. :)


>    - 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.

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.

-Dimitry


--Apple-Mail=_C5A7933F-460F-431A-BE05-C752275FCCFF
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-----
Version: GnuPG/MacGPG2 v2.0.26

iEUEARECAAYFAlSS0IYACgkQsF6jCi4glqPEdQCfVE7MItkXcaNthE+b/Y0AE1C6
btoAl0MSaWbjGLwTaC9ra/H7EMnGZQI=
=iLuy
-----END PGP SIGNATURE-----

--Apple-Mail=_C5A7933F-460F-431A-BE05-C752275FCCFF--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?D9C5A8D1-2158-4B37-9C9C-067A4DDE6E44>