Date: Mon, 10 Sep 2012 17:01:19 -0500 From: Brooks Davis <brooks@freebsd.org> To: Daniel Eischen <deischen@freebsd.org> Cc: toolchain@freebsd.org, current@freebsd.org Subject: Re: Clang as default compiler November 4th Message-ID: <20120910220119.GE64920@lor.one-eyed-alien.net> In-Reply-To: <Pine.GSO.4.64.1209101718570.16426@sea.ntplx.net> References: <20120910211207.GC64920@lor.one-eyed-alien.net> <Pine.GSO.4.64.1209101718570.16426@sea.ntplx.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--APlYHCtpeOhspHkB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Sep 10, 2012 at 05:22:37PM -0400, Daniel Eischen wrote: > On Mon, 10 Sep 2012, Brooks Davis wrote: >=20 > > [Please confine your replies to toolchain@freebsd.org to keep the thread > > on the most relevant list.] > > > > For the past several years we've been working towards migrating from > > GCC to Clang/LLVM as our default compiler. We intend to ship FreeBSD > > 10.0 with Clang as the default compiler on i386 and amd64 platforms. To > > this end, we will make WITH_CLANG_IS_CC the default on i386 and amd64 > > platforms on November 4th. > > > > What does the mean to you? > > > > * When you build world after the default is changed /usr/bin/cc, cpp, a= nd > > c++ will be links to clang. > > > > * This means the initial phase of buildworld and "old style" kernel > > compilation will use clang instead of gcc. This is known to work. > > > > * It also means that ports will build with clang by default. A major > > of ports work, but a significant number are broken or blocked by > > broken ports. For more information see: > > http://wiki.freebsd.org/PortsAndClang > > > > What issues remain? > > > > * The gcc->clang transition currently requires setting CC, CXX, and CPP > > in addition to WITH_CLANG_IS_CC. I will post a patch to toolchain@ > > to address this shortly. >=20 > I assume this will be done, tested and committed before 2012-11-04 > (or whenever the switchover date is). Pending review it will be done this week. > > * Ports compiler selection infrastructure is still under development. >=20 > This should be a prerequisite before making the switch, given > that ports will be broken without a work-around for building > them with gcc. We've defacto done that for more than a year. Some progress has resulted, but not enough. I will be helping fix ports and I hope others do as well. It's worth noting that a switchable compiler isn't a magic bullet. Many ports will need to be patched to support a compiler other than /usr/bin/cc or /usr/bin/gcc. -- Brooks --APlYHCtpeOhspHkB Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iD8DBQFQTmMuXY6L6fI4GtQRApXSAJ4yCIdCPurc1KZi3MO3koiWtbwt8ACffsXR eYjBdhIqqhYgWTV7JXrSarY= =rLLO -----END PGP SIGNATURE----- --APlYHCtpeOhspHkB--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120910220119.GE64920>