I have just finished building gcc 4.8.2 so that I can setup a cross compilation environment. Running the test suite generated a few errors and failures but I am not sure how to evaluate them. Here are the results I got: gcc.log:ERROR: Failed to mmap gcc.log:FAIL: varl is -1, not 6 g++.log:ERROR: Failed to mmap g++.log:FAIL: varl is -1, not 6 g++.log:FAIL: g++.old-deja/g++.mike/temp.C -std=c++98 execution test g++.log:FAIL: g++.old-deja/g++.mike/temp.C -std=c++11 execution test libmudflap.log:FAIL: libmudflap.c++/pass41-frag.cxx ( -O) execution test libmudflap.log:FAIL: libmudflap.c++/pass41-frag.cxx (-O2) execution test libmudflap.log:FAIL: libmudflap.c++/pass41-frag.cxx (-O3) execution test In looking at the results on http://gcc.gnu.org/buildstat.html it is hard to make much of the results. The "best" X86_64 4.8.2 build had just the libmudflap errors, but similar test results had hundreds of errors. As to my results, I can say that every X86_64 4.8.2 build I looked at failed the libmudflap pass41-frag.cxx test so I am guessing they are not a problem. I am not as sure of the others: Result Test ------ ----- Failed to mmap .../gcc/testsuite/c-c++-common/asan/rlimit-mmap-test-1.c varl is -1 .../gcc/testsuite/gcc.dg/guality/guality.exp ...c++98 execution tests. g++.old-deja/g++.mike/temp.C -std=c++98 execution test ...c++11 execution tests. g++.old-deja/g++.mike/temp.C -std=c++11 execution test My questions are 1. Are these failures a problem? 2. How can I find out what a particular test is for? 3. Should I submit my results to the buildstat people? Thanks Mark -- View this message in context: http://gcc.1065356.n5.nabble.com/Test-suite-results-what-they-mean-and-how-to-evaluate-tp1001613.html Sent from the gcc - Help mailing list archive at Nabble.com.
