From owner-freebsd-toolchain@FreeBSD.ORG Tue Sep 11 14:17:26 2012 Return-Path: Delivered-To: toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id F0E9E106566B; Tue, 11 Sep 2012 14:17:25 +0000 (UTC) (envelope-from koobs.freebsd@gmail.com) Received: from mail-qc0-f182.google.com (mail-qc0-f182.google.com [209.85.216.182]) by mx1.freebsd.org (Postfix) with ESMTP id 735A68FC1E; Tue, 11 Sep 2012 14:17:25 +0000 (UTC) Received: by qcsg15 with SMTP id g15so394164qcs.13 for ; Tue, 11 Sep 2012 07:17:24 -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=fnLkup1pRJuUBu7vFA0bwE7S9HIDojfXf3+dSq6/MWg=; b=Usw8VXHpLTdMVKyGCZQnAKSXkFDLfgt/V4TquR3mgLxOllk5Am/Ev9O0WEIbivKlUz AHk9QAoIZWfzzYcU4mHRY1qg0o1/fB+pwXcr+pTlHZyfeax5KZ1eVZqFtOSRQStbpxso 3ascurqd4uQwDkHP+D6B6N+VhGV09SWkPLP8PvVrBB8H98PpSnQmbQU57to5+pUQ/tXr 2SPzgpqkVPHo6OSNA68f1PnVwvuLXubEvXhdb5cBh6VMQ3n8+0to8nKsBdG6ZpCWsqFX UsFC7kPOJwJ6n6bWnxPzNOejFEN1SmijhFJ3xYFJK5ukhoRtuZxSL+nWhgqGHUxUaVWE rNmQ== MIME-Version: 1.0 Received: by 10.229.137.7 with SMTP id u7mr4705769qct.63.1347373044793; Tue, 11 Sep 2012 07:17:24 -0700 (PDT) Received: by 10.49.2.38 with HTTP; Tue, 11 Sep 2012 07:17:24 -0700 (PDT) In-Reply-To: <20120911140825.GA73518@lor.one-eyed-alien.net> References: <20120910211207.GC64920@lor.one-eyed-alien.net> <20120911104518.GF37286@deviant.kiev.zoral.com.ua> <20120911140825.GA73518@lor.one-eyed-alien.net> Date: Wed, 12 Sep 2012 00:17:24 +1000 Message-ID: From: koobs k To: Brooks Davis Content-Type: text/plain; charset=UTF-8 Cc: toolchain@freebsd.org, current@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: Tue, 11 Sep 2012 14:17:26 -0000 On 12 September 2012 00:08, Brooks Davis wrote: > On Tue, Sep 11, 2012 at 01:45:18PM +0300, Konstantin Belousov wrote: >> On Mon, Sep 10, 2012 at 04:12:07PM -0500, Brooks Davis wrote: >> > 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. >> > >> > * Ports compiler selection infrastructure is still under development. >> > >> > * Some ports could build with clang with appropriate tweaks. >> > >> > What can you do to help? >> > >> > * Switch (some of) your systems. Early adoption can help us find bugs. >> > >> > * Fix ports to build with clang. If you don't have a clang system, you >> > can use the CLANG/amd64 or CLANG/i386 build environments on >> > redports.org. >> > >> > tl;dr: Clang will become the default compiler for x86 architectures on 2012-11-04 >> >> There was a chorus of voices talking about ports already. My POV >> is that suggesting to 'fix remaining ports to work with clang' is >> just a nonsense. You are proposing to fork the development of all the >> programs which do not compile with clang. Often, upstream developers >> do not care about clang at all since it not being default compiler in >> Debian/Fedora/Whatever Linux. The project simply do not have resources >> to maintain the fork of 20K programs. > > I may have phrased the above poorly, but in most cases I'd be happy with > using USE_GCC as a solution, but to the extent that port maintainers > can fix their ports to build with clang, that's a good thing. Having a > deadline will help focus efforts towards finding the right fix for the > most important ports in a timely manner. On that note, just identified the issue with multimedia/x264 and have submitted a PR for it (ports/171542) It also highlighted a missing libprofile_rt.a in base clang that theraven has pinged dim@ about ~448 less affected ports to worry about now :) --Koobs