search for: _getclangcmakebuildfactory

...phase 1 build with the current release, that seems perfectly reasonable; but again, it's probably best encoded with a zorg change specifically for that case. (I don't want to add too many magical layers of CMake option overrides for two-phase builds...) [*] I'm specifically looking at _getClangCMakeBuildFactory here: http://llvm.org/svn/llvm-project/zorg/trunk/zorg/buildbot/builders/ClangBuilder.py -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160322/11fec36d/attachment.html>

...uild with the current release, that seems perfectly reasonable; but again, it's probably best encoded with a zorg change specifically for that case. (I don't want to add too many magical layers of CMake option overrides for two-phase builds...) > > [*] I'm specifically looking at _getClangCMakeBuildFactory here: > http://llvm.org/svn/llvm-project/zorg/trunk/zorg/buildbot/builders/ClangBuilder.py <http://llvm.org/svn/llvm-project/zorg/trunk/zorg/buildbot/builders/ClangBuilder.py>_______________________________________________ > LLVM Developers mailing list > llvm-dev at lists.llvm.org &...

My thought was that its reasonable to expect no warnings when building from bootstrap (as you say) and the last release of Clang. Generally, I think we should work around warnings in the last release of Clang if only for the convenience of folks using that release to build stage1 and using Werror. Certainly, we tend to fix warnings even from earlier Clang versions and from GCC in order to keep