On Wed, Dec 4, 2013 at 2:06 PM, Ted Byers <r.ted.byers@xxxxxxxxx> wrote: > > |guality/pr41558.f90 -O0 line 7 s == 'foo' > FAIL: gfortran.dg/guality/pr41558.f90 -O1 line 7 s == 'foo' > FAIL: gfortran.dg/guality/pr41558.f90 -O2 line 7 s == 'foo' > FAIL: gfortran.dg/guality/pr41558.f90 -O3 -fomit-frame-pointer line 7 s == > 'foo' > FAIL: gfortran.dg/guality/pr41558.f90 -O3 -fomit-frame-pointer > -funroll-loops line 7 s == 'foo' > FAIL: gfortran.dg/guality/pr41558.f90 -O3 -fomit-frame-pointer > -funroll-all-loops -finline-functions line 7 s == 'foo' > FAIL: gfortran.dg/guality/pr41558.f90 -O3 -g line 7 s == 'foo' > FAIL: gfortran.dg/guality/pr41558.f90 -Os line 7 s == 'foo' You can safely ignore all guality test failures. They are very dependent on the version of gdb on your system. > === libmudflap tests === > > > Running target unix > FAIL: libmudflap.c++/pass41-frag.cxx ( -O) execution test > FAIL: libmudflap.c++/pass41-frag.cxx (-O2) execution test > FAIL: libmudflap.c++/pass41-frag.cxx (-O3) execution test You can safely ignore all libmudflap test failures. They are somewhat erratic. I believe libmudflap is actually being removed. > > Does the output above provide the information to explain what went awry > during the |make -k| check command? If so, I'd like to understand... If you > obtained the above output, would you feel confident enough in the build of > gcc to proceed with installing it and using it, even in a production > environment? Yes. > One last question about the output from test-summary. Right after the above > output, I saw the following: > > |Mail -s "Results for 4.8.2 testsuite on x86_64-unknown-linux-gnu" > gcc-testresults@xxxxxxxxxxx && mv > ... > What, exactly, is that doing, and why? I would only expect to see that if you ran "make mail-report.log". I don't know why it would happen if you only ran "make check". In any case those commands don't actually send mail, they just tell you what to run if you want to send mail. Ian
