[LLVMdev] [cfe-dev] Living on Clang

[Douglas Gregor]

On Apr 15, 2010, at 7:32 AM, Kenneth Uildriks wrote:

> I can't switch to clang on my project until it can handle boost headers.

The intent of using Clang for LLVM & Clang development is that we can improve compiler quality (diagnostics, debugging, etc.) on a code base where Clang works reasonably well already.

For other code bases, we're likely to have more basic problems---rejecting valid code, complaining about ill-formed code that GCC accepts, horrid miscompilations, etc.---so we get a different kind of feedback. For Boost specifically, we have a tracking bug (http://llvm.org/bugs/show_bug.cgi?id=6023) and are interested in reduced problems that show up in Boost libraries [*].

	- Doug

[*] Actually, we're *particularly* interested in Boost since there will be a Clang talk at BoostCon this year. Check it out at  http://www.boostcon.com/home .

> On Thu, Apr 15, 2010 at 2:17 AM, Rene Rebe <rene at exactcode.de> wrote:
>> Hi,
>> 
>> On Apr 14, 2010, at 10:51 PM, Douglas Gregor wrote:
>> 
>>> Hello fellow LLVMers and Clangstas,
>>> 
>>> We want to make Clang great, and we need your help!
>>> 
>>> Helping is easy: just build Clang on your platform and start using it as your main compiler for LLVM and Clang development. Much of the Clang team has been living on Clang for at least several weeks already, and we've found it to be quite stable for development. If you run into problems---poor diagnostics, poor debugging experience, compiler crashes, rejecting valid code, whatever---please file Bugzillas so we can get them fixed.
>> 
>> Been there, done that: http://rene.rebe.de/2010-02-16/llvm-clang-support-in-t2-sde-linux/
>> 
>> And reported C++ issues spotted while at it. I plan to further extend the testing and potentially default to Clang (without GCC) in a future T2 Linux revision.
>> 
>>> Steps to living on Clang:
>>> 
>>>  - Make sure you're getting a good revision of Clang/LLVM from Subversion by checking the Buildbots (http://google1.osuosl.org:8011/console). The clang-*-selfhost builds have passed self-host + testing and are good candidates.
>>> 
>>>  - Build Clang as part of LLVM (http://clang.llvm.org/get_started.html). I suggest a Release build, since Debug builds tend to be very slow.
>>> 
>>>  - Install Clang + LLVM somewhere that isn't where you do your normal LLVM/Clang development.
>>> 
>>>  - Configure with the environment variables CC=/path/to/clang CXX=/path/to/clang++, which works with either autoconf configure or CMake cmake/ccmake.
>>> 
>>>  - Build LLVM and Clang as normal.
>>> 
>>>  - Report your experiences to help us improve Clang!
>>> 
>>>       - Doug
>> 
>> --
>>  René Rebe, ExactCODE GmbH, Jaegerstr. 67, DE-10117 Berlin
>>  http://exactcode.com | http://t2-project.org | http://rene.rebe.de
>> 
>> 
>> _______________________________________________
>> LLVM Developers mailing list
>> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
>> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
>>