On Sep 9, 2014, at 1:50 PM, [email protected] wrote:
>
> Il 09/09/2014 05:44, Robert Xu ha scritto:
>> * Yes, we have switched to LLVM/Clang as our default compiler for
>> 2015.0. You don't have to use it; simply set CC=gcc and CXX=g++ in
>> your spec file.
> This would be awesome, but can you tell me what is the point in switching
> between 2 bad compilers at the build time?
> Clang is too young and unstable, full of bugs, the gcc4.9 that we have in
> cooker
> is worse then vanilla , so you ware saying?
>
So which devil do you want? gcc4? clang? gcc5? It's hard to tell what
you wish to see happen from your statements.
FYI
I'm compiling rpm with clang 3.5 atm on CentOS6/x86_64 and running
regression tests like
Install OWL3 in a chroot.
Several ancient bugs were instantly identified using -fsanitize=address.
And leak detection with ASAN_OPTIONS is far far faster than using
valgrind. Yes the leakchecker "works" only on x86_64.
>From what I am seeing, I can probably run rpm insturmented
with -fsanitize=address everywhere and always.
On to adding OPENMP to clang-3.5 to see how good the thread deadlock
detector atucally is.
73 de Jeff
_______________________________________________
OM-Cooker mailing list
[email protected]
http://ml.openmandriva.org/listinfo.cgi/om-cooker-openmandriva.org
