[llvm-commits] [llvm] r149800 - in /llvm/trunk: include/llvm/ include/llvm/Analysis/ lib/Analysis/ lib/AsmParser/ lib/Bitcode/Writer/ lib/CodeGen/AsmPrinter/ lib/CodeGen/SelectionDAG/ lib/Target/CBackend/ lib/Target/CppBackend/ lib/Transforms/Instrumentation/ lib/Transforms/Scalar/ lib/VMCore/ tools/bugpoint/ tools/lto/

[Duncan Sands]

Hi Benjamin,

>>> This commit is causing our llvm-gcc build bot to fail at stage 1.
>>
>> I'm getting rid of the two llvm-gcc buildbots
>>
>>    http://lab.llvm.org:8011/builders/llvm-gcc-i386-linux-selfhost
>>    http://lab.llvm.org:8011/builders/llvm-x86_64-linux-checks
>>
>> today.  Do we really want to keep any llvm-gcc buildbots?
>
> +1 on axing the llvm-gcc buildbots, in the last few months the number of required API fixes was a lot bigger than the number of real problems these two bots detected.
>
> Can they be converted into clang/dragonegg builders? We don't have a clang-i386-selfhost and no other -checks bot at the moment and both configurations sound useful.

I've converted the lab.llvm.org llvm-gcc buildbots into dragonegg buildbots
(including an expensive checks one).  There are several spare x86-64 hosts in
the gcc compile farm (see the list in 
zorg/buildbot/osuosl/master/config/slaves.py) which can be used for a 
clang-i386-selfhost if someone wants to set
one up (you can do an i386 self-host on an x86-64 machine by using -m32 and
configuring llvm for the right target).

Ciao, Duncan.