From owner-freebsd-toolchain@FreeBSD.ORG Mon Sep 10 22:35:08 2012 Return-Path: Delivered-To: toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 38A871065675; Mon, 10 Sep 2012 22:35:08 +0000 (UTC) (envelope-from break19@gmail.com) Received: from mail-ob0-f182.google.com (mail-ob0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id C950F8FC08; Mon, 10 Sep 2012 22:35:07 +0000 (UTC) Received: by obbun3 with SMTP id un3so4846721obb.13 for ; Mon, 10 Sep 2012 15:35:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=A2TLPDKr3uqxwHQtPuLWIZyLV1tTolAbSIiQZS5nc60=; b=WZaJzbjz8WiMR0JoEbraEvz7wBbNvGUCHTeHz3iDsAUTPkKHvXmSkQABUTciv7YP5/ ygb0PJ0HYoalFbm2aCfEAx4dt/dOwXRliInUHZIqs27a9A3iHYjlt4GNz2UQunMJV23W FMx0pqTJukNoeuHxtOy1R3yuLT8Lz7WiiyNMi+0Ep0XP9sjJukckmyH5jtoWGGzcAhQw OW90UTy+POL3SE+TWrrtYlcflALn8SESCHKBwfOFOuBmbsvkVhLuh/JLX7MI7x9V6tgi oZ05Bm9XY83Sw4sy2jiclMkK45HuYPE3qDPObVK2v8+NXvV2T6CMdF8kaQdTjhjG7GTC u1jQ== MIME-Version: 1.0 Received: by 10.60.13.104 with SMTP id g8mr15670305oec.82.1347316507007; Mon, 10 Sep 2012 15:35:07 -0700 (PDT) Received: by 10.76.2.202 with HTTP; Mon, 10 Sep 2012 15:35:06 -0700 (PDT) In-Reply-To: <20120910220119.GE64920@lor.one-eyed-alien.net> References: <20120910211207.GC64920@lor.one-eyed-alien.net> <20120910220119.GE64920@lor.one-eyed-alien.net> Date: Mon, 10 Sep 2012 17:35:06 -0500 Message-ID: From: Chuck Burns To: Brooks Davis Content-Type: text/plain; charset=ISO-8859-1 Cc: Daniel Eischen , toolchain@freebsd.org Subject: Re: Clang as default compiler November 4th X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Sep 2012 22:35:08 -0000 On Mon, Sep 10, 2012 at 5:01 PM, Brooks Davis wrote: > On Mon, Sep 10, 2012 at 05:22:37PM -0400, Daniel Eischen wrote: >> On Mon, 10 Sep 2012, Brooks Davis wrote: >> >> > [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, and >> > 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. >> >> 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. >> >> 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 This is actually a pretty good thing. Because -before- it's the default compiler, some ports maintainers (and even more upstreams) have the attitude of "My port works fine" until it no longer does.. bringing this change will make a few of these people realize that we are -serious- about switching to clang. For those worrying about "zomg, my system wont work?!" Remember.. This is a -current thing. If you're running bleeding edge, you have to expect to get cut every now and then. -- Chuck Burns