Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 12 Sep 2012 00:17:24 +1000
From:      koobs k <koobs.freebsd@gmail.com>
To:        Brooks Davis <brooks@freebsd.org>
Cc:        toolchain@freebsd.org, current@freebsd.org
Subject:   Re: Clang as default compiler November 4th
Message-ID:  <CAKA3KycrQ3Vr4K4-K7wOEds04SApp9j7gF4aL=JQFJ2KFhmNqg@mail.gmail.com>
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>

next in thread | previous in thread | raw e-mail | index | archive | help
On 12 September 2012 00:08, Brooks Davis <brooks@freebsd.org> 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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAKA3KycrQ3Vr4K4-K7wOEds04SApp9j7gF4aL=JQFJ2KFhmNqg>