<div dir="ltr">I doubt any of the buildbots are running such recent versions of GCC - probably just whatever's common/default on various distros like Ubuntu. <br><br>Adding a buildbot that covers them wouldn't be a bad idea.</div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Mar 9, 2016 at 12:55 AM, Mikael Holmén <span dir="ltr"><<a href="mailto:cfe-dev@lists.llvm.org" target="_blank">cfe-dev@lists.llvm.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
Are there any buildbots that build clang/llvm with gcc and run tests nowadays?<br>
<br>
When testing our out-of-tree target we are regularly building the compiler with both clang and gcc and lately we have noticed an increasing number of problems when using gcc which the rest of the community doesn't seem to notice?<br>
<br>
E.g. for some days now at top-of-tree, if building with gcc 4.9.1 or 5.1.0 one test case fails with SEGV:<br>
<br>
FAIL: Clang-Unit :: ASTMatchers/ASTMatchersTests/IsAnyPointer.MatchesObjcPointer (8218 of 25131)<br>
******************** TEST 'Clang-Unit :: ASTMatchers/ASTMatchersTests/IsAnyPointer.MatchesObjcPointer' FAILED ********************<br>
Note: Google Test filter = IsAnyPointer.MatchesObjcPointer<br>
[==========] Running 1 test from 1 test case.<br>
[----------] Global test environment set-up.<br>
[----------] 1 test from IsAnyPointer<br>
[ RUN      ] IsAnyPointer.MatchesObjcPointer<br>
#0 0x00000000005b4f15 llvm::sys::PrintStackTrace(llvm::raw_ostream&) (/repo/bbijenkins/bbi-sw-stable-jenkins/workspace/llvm-master/build-all-gcc49/tools/clang/unittests/ASTMatchers/ASTMatchersTests+0x5b4f15)<br>
#1 0x00000000005b2bc6 llvm::sys::RunSignalHandlers() (/repo/bbijenkins/bbi-sw-stable-jenkins/workspace/llvm-master/build-all-gcc49/tools/clang/unittests/ASTMatchers/ASTMatchersTests+0x5b2bc6)<br>
#2 0x00000000005b2dda SignalHandler(int) (/repo/bbijenkins/bbi-sw-stable-jenkins/workspace/llvm-master/build-all-gcc49/tools/clang/unittests/ASTMatchers/ASTMatchersTests+0x5b2dda)<br>
#3 0x00007f194f891810 __restore_rt (/lib64/libpthread.so.0+0xf810)<br>
#4 0x00000000005463a0 clang::ast_matchers::IsAnyPointer_MatchesObjcPointer_Test::TestBody() (/repo/bbijenkins/bbi-sw-stable-jenkins/workspace/llvm-master/build-all-gcc49/tools/clang/unittests/ASTMatchers/ASTMatchersTests+0x5463a0)<br>
#5 0x00000000005d3e02 testing::Test::Run() (/repo/bbijenkins/bbi-sw-stable-jenkins/workspace/llvm-master/build-all-gcc49/tools/clang/unittests/ASTMatchers/ASTMatchersTests+0x5d3e02)<br>
<br>
So, are there any buildbots that should notice this or have everyone stopped using gcc?<br>
<br>
Best regards,<br>
Mikael<br>
_______________________________________________<br>
cfe-dev mailing list<br>
<a href="mailto:cfe-dev@lists.llvm.org" target="_blank">cfe-dev@lists.llvm.org</a><br>
<a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev" rel="noreferrer" target="_blank">http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev</a><br>
</blockquote></div><br></div>